Playwright Pro

Playwright Pro

Production-grade end-to-end testing with Playwright. Generate tests from user stories, implement the Page Object pattern for maintainability, apply the correct locator strategy for resilient tests, diagnose and fix flaky tests, migrate from Cypress or Selenium, integrate with CI/CD, run visual regression tests, and perform accessibility audits. Enforces the 10 golden rules that eliminate 90% of E2E test failures.

Core Capabilities

• Resilient authoring — getByRole/getByLabel/getByText locator priority, web-first auto-retrying assertions, and the 10 golden rules.
• Page Object Model — centralize locators, expose user-intent methods, generate POM classes from HTML/selectors.
• Test generation — produce specs from user stories with happy-path and error-path coverage.
• Flaky-test diagnosis — trace analysis, headed/debug runs, race-condition and shared-state fixes.
• Migration — Cypress/Selenium → Playwright command mapping and auth-setup patterns.
• CI integration — GitHub Actions, sharding, conditional browser installs, trace/screenshot artifacts.
• Visual regression & accessibility — toHaveScreenshot baselines and Axe WCAG AA gates.

When to Use

• Writing or organizing E2E tests for web apps.
• Fixing flaky tests or diagnosing CI-only failures.
• Migrating a suite from Cypress or Selenium.
• Adding visual regression or WCAG accessibility gates.
• Setting up Playwright CI integration and reporting.

Clarify First

Before generating tests, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• Task / sub-skill — init, generate, fix-flaky, migrate, or review (routes the entire workflow)
• User story or flow to cover — the happy + error paths the spec must assert (drives test generation)
• Locator surface — whether the app exposes roles/labels/data-testid (sets locator strategy and POM resilience)
• Source framework (if migrating) — Cypress or Selenium (selects the command-mapping table)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Sub-Skills

This skill uses compound sub-skill architecture. Each sub-skill in skills/ handles a specific workflow:

Sub-skill flow: Init → Generate → Review → Fix (if needed); Coverage → Generate (fill gaps); Report → BrowserStack / TestRail.

Tools

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

• references/core-rules-and-patterns.md — the 10 golden rules, locator priority, playwright.config.ts, Page Object Model classes, test generation from user stories, and shared-auth setup. Read when authoring tests or configuring a project.
• references/playwright-patterns.md — locator decision tree, web-first vs non-retrying assertion patterns, custom/worker fixtures, network mocking, anti-pattern quick reference, and CI sharding patterns. Read when choosing locators, mocking APIs, or building fixtures.
• references/diagnosis-migration-and-ci.md — flaky-test causes/fixes and diagnosis commands, Cypress→Playwright migration table, GitHub Actions CI, visual regression, accessibility testing, common pitfalls, best practices, troubleshooting table, and the success-criteria bar. Read when fixing flaky tests, migrating, wiring CI, or auditing a suite.

Scope & Limitations

This skill covers:

• End-to-end test authoring, organization, and maintenance with Playwright
• Page Object Model architecture and locator strategy best practices
• Flaky test diagnosis, CI integration, and trace-based debugging
• Visual regression testing and WCAG accessibility auditing

This skill does NOT cover:

• Unit testing or component testing in isolation (see engineering/testing-strategy for test pyramid guidance)
• API contract testing or load/performance testing (see api-test-suite-builder for API-focused testing)
• Test data management, database seeding, or factory patterns for test fixtures
• Mobile native app testing (Appium, Detox); this skill targets web browsers only

Integration Points