Playwright Pro
Production-grade Playwright testing toolkit for AI coding agents.
Available Commands
When installed as a Claude Code plugin, these are available as /pw: commands:
| Command |
What it does |
/pw:init |
Set up Playwright — detects framework, generates config, CI, first test |
/pw:generate <spec> |
Generate tests from user story, URL, or component |
/pw:review |
Review tests for anti-patterns and coverage gaps |
/pw:fix <test> |
Diagnose and fix failing or flaky tests |
/pw:migrate |
Migrate from Cypress or Selenium to Playwright |
/pw:coverage |
Analyze what's tested vs. what's missing |
/pw:testrail |
Sync with TestRail — read cases, push results |
/pw:browserstack |
Run on BrowserStack, pull cross-browser reports |
/pw:report |
Generate test report in your preferred format |
Quick Start Workflow
The recommended sequence for most projects:
1. /pw:init → scaffolds config, CI pipeline, and a first smoke test
2. /pw:generate → generates tests from your spec or URL
3. /pw:review → validates quality and flags anti-patterns ← always run after generate
4. /pw:fix <test> → diagnoses and repairs any failing/flaky tests ← run when CI turns red
Validation checkpoints:
- After
/pw:generate — always run /pw:review before committing; it catches locator anti-patterns and missing assertions automatically.
- After
/pw:fix — re-run the full suite locally (npx playwright test) to confirm the fix doesn't introduce regressions.
- After
/pw:migrate — run /pw:coverage to confirm parity with the old suite before decommissioning Cypress/Selenium tests.
Example: Generate → Review → Fix
# 1. Generate tests from a user story
/pw:generate "As a user I can log in with email and password"
# Generated: tests/auth/login.spec.ts
# → Playwright Pro creates the file using the auth template.
# 2. Review the generated tests
/pw:review tests/auth/login.spec.ts
# → Flags: one test used page.locator('input[type=password]') — suggests getByLabel('Password')
# → Fix applied automatically.
# 3. Run locally to confirm
npx playwright test tests/auth/login.spec.ts --headed
# 4. If a test is flaky in CI, diagnose it
/pw:fix tests/auth/login.spec.ts
# → Identifies missing web-first assertion; replaces waitForTimeout(2000) with expect(locator).toBeVisible()
Golden Rules
getByRole() over CSS/XPath — resilient to markup changes- Never
page.waitForTimeout() — use web-first assertions
expect(locator) auto-retries; expect(await locator.textContent()) does not- Isolate every test — no shared state between tests
baseURL in config — zero hardcoded URLs- Retries:
2 in CI, 0 locally
- Traces:
'on-first-retry' — rich debugging without slowdown
- Fixtures over globals —
test.extend() for shared state
- One behavior per test — multiple related assertions are fine
- Mock external services only — never mock your own app
Locator Priority
1. getByRole() — buttons, links, headings, form elements
2. getByLabel() — form fields with labels
3. getByText() — non-interactive text
4. getByPlaceholder() — inputs with placeholder
5. getByTestId() — when no semantic option exists
6. page.locator() — CSS/XPath as last resort
What's Included
- 9 skills with detailed step-by-step instructions
- 3 specialized agents: test-architect, test-debugger, migration-planner
- 55 test templates: auth, CRUD, checkout, search, forms, dashboard, settings, onboarding, notifications, API, accessibility
- 2 MCP servers (TypeScript): TestRail and BrowserStack integrations
- Smart hooks: auto-validate test quality, auto-detect Playwright projects
- 6 reference docs: golden rules, locators, assertions, fixtures, pitfalls, flaky tests
- Migration guides: Cypress and Selenium mapping tables
Integration Setup
TestRail (Optional)
export TESTRAIL_URL="https://your-instance.testrail.io"
export TESTRAIL_USER="your@email.com"
export TESTRAIL_API_KEY="your-api-key"
BrowserStack (Optional)
export BROWSERSTACK_USERNAME="your-username"
export BROWSERSTACK_ACCESS_KEY="your-access-key"
Quick Reference
See reference/ directory for:
golden-rules.md — The 10 non-negotiable ruleslocators.md — Complete locator priority with cheat sheetassertions.md — Web-first assertions referencefixtures.md — Custom fixtures and storageState patternscommon-pitfalls.md — Top 10 mistakes and fixesflaky-tests.md — Diagnosis commands and quick fixes
See templates/README.md for the full template index.
1---2name: playwright-pro3description: Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from C...4license: MIT5---67# Playwright Pro89Production-grade Playwright testing toolkit for AI coding agents.1011## Available Commands1213When installed as a Claude Code plugin, these are available as `/pw:` commands:1415| Command | What it does |16|---|---|17| `/pw:init` | Set up Playwright — detects framework, generates config, CI, first test |18| `/pw:generate <spec>` | Generate tests from user story, URL, or component |19| `/pw:review` | Review tests for anti-patterns and coverage gaps |20| `/pw:fix <test>` | Diagnose and fix failing or flaky tests |21| `/pw:migrate` | Migrate from Cypress or Selenium to Playwright |22| `/pw:coverage` | Analyze what's tested vs. what's missing |23| `/pw:testrail` | Sync with TestRail — read cases, push results |24| `/pw:browserstack` | Run on BrowserStack, pull cross-browser reports |25| `/pw:report` | Generate test report in your preferred format |2627## Quick Start Workflow2829The recommended sequence for most projects:3031```321. /pw:init → scaffolds config, CI pipeline, and a first smoke test332. /pw:generate → generates tests from your spec or URL343. /pw:review → validates quality and flags anti-patterns ← always run after generate354. /pw:fix <test> → diagnoses and repairs any failing/flaky tests ← run when CI turns red36```3738**Validation checkpoints:**39- After `/pw:generate` — always run `/pw:review` before committing; it catches locator anti-patterns and missing assertions automatically.40- After `/pw:fix` — re-run the full suite locally (`npx playwright test`) to confirm the fix doesn't introduce regressions.41- After `/pw:migrate` — run `/pw:coverage` to confirm parity with the old suite before decommissioning Cypress/Selenium tests.4243### Example: Generate → Review → Fix4445```bash46# 1. Generate tests from a user story47/pw:generate "As a user I can log in with email and password"4849# Generated: tests/auth/login.spec.ts50# → Playwright Pro creates the file using the auth template.5152# 2. Review the generated tests53/pw:review tests/auth/login.spec.ts5455# → Flags: one test used page.locator('input[type=password]') — suggests getByLabel('Password')56# → Fix applied automatically.5758# 3. Run locally to confirm59npx playwright test tests/auth/login.spec.ts --headed6061# 4. If a test is flaky in CI, diagnose it62/pw:fix tests/auth/login.spec.ts63# → Identifies missing web-first assertion; replaces waitForTimeout(2000) with expect(locator).toBeVisible()64```6566## Golden Rules67681. `getByRole()` over CSS/XPath — resilient to markup changes692. Never `page.waitForTimeout()` — use web-first assertions703. `expect(locator)` auto-retries; `expect(await locator.textContent())` does not714. Isolate every test — no shared state between tests725. `baseURL` in config — zero hardcoded URLs736. Retries: `2` in CI, `0` locally747. Traces: `'on-first-retry'` — rich debugging without slowdown758. Fixtures over globals — `test.extend()` for shared state769. One behavior per test — multiple related assertions are fine7710. Mock external services only — never mock your own app7879## Locator Priority8081```821. getByRole() — buttons, links, headings, form elements832. getByLabel() — form fields with labels843. getByText() — non-interactive text854. getByPlaceholder() — inputs with placeholder865. getByTestId() — when no semantic option exists876. page.locator() — CSS/XPath as last resort88```8990## What's Included9192- **9 skills** with detailed step-by-step instructions93- **3 specialized agents**: test-architect, test-debugger, migration-planner94- **55 test templates**: auth, CRUD, checkout, search, forms, dashboard, settings, onboarding, notifications, API, accessibility95- **2 MCP servers** (TypeScript): TestRail and BrowserStack integrations96- **Smart hooks**: auto-validate test quality, auto-detect Playwright projects97- **6 reference docs**: golden rules, locators, assertions, fixtures, pitfalls, flaky tests98- **Migration guides**: Cypress and Selenium mapping tables99100## Integration Setup101102### TestRail (Optional)103```bash104export TESTRAIL_URL="https://your-instance.testrail.io"105export TESTRAIL_USER="your@email.com"106export TESTRAIL_API_KEY="your-api-key"107```108109### BrowserStack (Optional)110```bash111export BROWSERSTACK_USERNAME="your-username"112export BROWSERSTACK_ACCESS_KEY="your-access-key"113```114115## Quick Reference116117See `reference/` directory for:118- `golden-rules.md` — The 10 non-negotiable rules119- `locators.md` — Complete locator priority with cheat sheet120- `assertions.md` — Web-first assertions reference121- `fixtures.md` — Custom fixtures and storageState patterns122- `common-pitfalls.md` — Top 10 mistakes and fixes123- `flaky-tests.md` — Diagnosis commands and quick fixes124125See `templates/README.md` for the full template index.
nous-hermeshub