playwright-qa-cli

Automate web application QA testing with Playwright CLI headless browser tests.

Updated Mar 11, 2026

Search Tags:#automation #testing #qa #cli #web testing #playwright

Ready to run

npx skills add https://github.com/8GG-Git/Test_Team --skill playwright-qa-cli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: playwright-qa-cli
Source: https://github.com/8GG-Git/Test_Team/tree/main/skills/playwright-qa-cli
Command: npx skills add https://github.com/8GG-Git/Test_Team --skill playwright-qa-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of Quality Assurance testing for web applications using the Playwright CLI, ensuring consistent and reliable verification of features and bug fixes.

Core Features & Use Cases

Headless Browser Testing: Executes tests in a headless browser environment for efficiency.
End-to-End Workflow: Provisions test users, logs in, navigates pages, takes screenshots, and generates reports.
Verification Modes: Supports verify mode to reproduce bugs and check mode to confirm fixes.
Use Case: When a bug is reported, use this Skill in verify mode to automatically reproduce the issue, capture evidence, and then use check mode after a fix is deployed to confirm the bug is resolved.

Quick Start

Use the playwright-qa-cli skill to verify the bug on the dashboard page in production.

Frequently Asked Questions about playwright-qa-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate QA testing with Playwright CLI for web applications?▼

Automating QA testing with Playwright CLI involves executing headless browser tests to verify web application features. This process provisions test users, handles authentication, navigates pages, captures screenshots, and generates validation reports.

What is the difference between verify and check modes in Playwright testing?▼

In Playwright testing, verify mode reproduces reported bugs to capture evidence of the issue, while check mode confirms that a deployed fix successfully resolves the bug. Both modes automate headless browser execution for validation.

Can I use Supabase for user management when running end-to-end web tests?▼

Yes, you can use Supabase for user management during end-to-end web tests. The testing workflow integrates with Supabase to provision test users and handle authentication before executing Playwright CLI commands.

How do I set up the environment for running Playwright CLI commands?▼

Setting up the environment for Playwright CLI commands requires configuring the PATH and specifying settings via a CONFIG.md file. These bash execution prerequisites ensure the headless browser tests run successfully.

What is the best way to capture evidence of a bug during headless browser testing?▼

The best way to capture bug evidence during headless browser testing is using verify mode. This mode automatically reproduces the reported issue, takes screenshots of the affected pages, and generates reports.

Does Playwright CLI testing support user authentication and navigation workflows?▼

Playwright CLI testing supports user authentication and navigation workflows. It provisions test users, logs them in, navigates through application pages, and takes screenshots to verify end-to-end functionality.