playwright-pro

Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test mi...

Security Scan

Playwright Pro's files, instructions, hooks, and optional integrations are consistent with a Playwright testing toolkit, with only a minor mismatch between declared requirements and the actual tools the included scripts expect.

Purpose & Capability

The skill's name, description, SKILL.md, agents, hooks, templates, and MCP integration code all align with a Playwright testing toolkit (generate/review/fix/migrate, optional TestRail and BrowserStack). One small inconsistency: registry metadata lists no required binaries, but shipped scripts and agents assume common developer tools (bash, python3, node/npx/tsx) — these are reasonable for this purpose but were not declared.

Instruction Scope

SKILL.md and agent docs confine work to test-generation, review, debugging, migration, and optional integration calls. Hooks and agents read project files, run Playwright commands, and validate tests — all within the stated scope. There are no instructions to collect or transmit unrelated secrets or to phone home outside the described integrations (BrowserStack/TestRail), and those integrations require explicit env vars.

Install Mechanism

There is no remote install/download step (instruction-only with local code files). The included code and shell hooks live in the skill bundle and will be executed locally by the agent runtime if invoked. No external arbitrary downloads or URL-extract installs are present in the manifest.

Credentials

The skill declares no required environment variables in metadata, and TestRail/BrowserStack credentials are documented as optional. The MCP server code reads TESTRAIL_* and BROWSERSTACK_* env vars if you choose to run those servers — this is proportionate. Note: although optional, these env vars would grant network access to those third-party APIs, so only set them if you intend to use those integrations.

Persistence & Privilege

always:false and the skill does not demand persistent platform-level privileges. The hooks will run at SessionStart and after Write/Edit (per hooks.json) which is expected for a plugin that auto-detects Playwright projects and validates test files. The skill does not modify other skills' configs or request platform-wide credentials.

Assessment

This skill appears to be what it says: a Playwright-focused toolkit with templates, agents, hooks, and optional TestRail/BrowserStack integrations. Before installing: 1) Understand that session hooks will run included shell scripts (detect-playwright.sh and validate-test.sh) which read files in your project and emit warnings — they do not exfiltrate data. 2) The package includes MCP server code you can run locally to connect to TestRail/BrowserStack; those servers require you to set TESTRAIL_* or BROWSERSTACK_* environment variables and will then contact those external APIs — only provide those credentials if you trust the service and intend to use it. 3) Ensure your environment has common developer binaries (bash, python3, node/npx/tsx) because the scripts and example commands assume them even though the registry metadata doesn't list required binaries. 4) If you want to be extra cautious, review the included scripts (hooks/*.sh) and MCP server source files before running any server processes or setting credentials.

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

1. getByRole() over CSS/XPath — resilient to markup changes
2. Never page.waitForTimeout() — use web-first assertions
3. expect(locator) auto-retries; expect(await locator.textContent()) does not
4. Isolate every test — no shared state between tests
5. baseURL in config — zero hardcoded URLs
6. Retries: 2 in CI, 0 locally
7. Traces: 'on-first-retry' — rich debugging without slowdown
8. Fixtures over globals — test.extend() for shared state
9. One behavior per test — multiple related assertions are fine
10. 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="[e-mail]"
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 rules
• locators.md — Complete locator priority with cheat sheet
• assertions.md — Web-first assertions reference
• fixtures.md — Custom fixtures and storageState patterns
• common-pitfalls.md — Top 10 mistakes and fixes
• flaky-tests.md — Diagnosis commands and quick fixes

See templates/README.md for the full template index.