playwright-pro

What This Skill Does

Playwright Pro is a production-grade testing toolkit specifically designed for AI coding agents to streamline browser automation and end-to-end (E2E) testing workflows. It transforms raw user stories into robust, maintainable test suites. By leveraging 55 specialized templates and automated analysis agents, the skill handles the heavy lifting of framework initialization, test generation, anti-pattern detection, and complex migration tasks. It provides a suite of CLI-based commands that allow agents to intelligently scaffold configurations, identify locator bottlenecks, fix flaky tests, and integrate seamlessly with external platforms like TestRail and BrowserStack. It serves as an end-to-end lifecycle management tool for your testing infrastructure.

Installation

To integrate this skill into your environment, use the OpenClaw CLI to install the package from the official source repository:

clawhub install openclaw/skills/skills/alirezarezvani/cs-pw

Once installed, the /pw: command namespace becomes available to your AI agent, enabling direct command execution within your workspace.

Use Cases

Playwright Pro is designed for developers, QA engineers, and DevOps teams aiming to modernize their testing strategy. Key use cases include:

• Greenfield Setup: Quickly scaffolding Playwright projects with optimized CI/CD pipelines.
• Migration: Transitioning legacy Cypress or Selenium suites to Playwright with high parity.
• Maintenance: Automatically diagnosing flaky tests and refactoring brittle locators (e.g., swapping CSS selectors for getByRole or getByLabel).
• Quality Assurance: Ensuring test suites meet modern standards via the /pw:review command which catches missing assertions and anti-patterns.
• Enterprise Integration: Synchronizing test results with TestRail for compliance and running cross-browser tests on BrowserStack.

Example Prompts

1. "Initialize a new Playwright project in this repo and create a smoke test for the user login flow."
2. "My login test is failing intermittently in CI; please use /pw:fix to diagnose and repair it."
3. "We are moving away from Cypress; please run /pw:migrate on our current e2e folder to convert the existing tests to Playwright."

Tips & Limitations

• Validation Workflow: Always follow the Generate → Review → Fix sequence. The /pw:review command is your primary defense against brittle tests.
• Assertions: Prefer web-first assertions like expect(locator).toBeVisible() over static timeouts. The tool automatically suggests these corrections.
• Coverage: Run /pw:coverage frequently during migration projects to identify gaps between your legacy suite and your new Playwright implementation.
• Limitations: While highly capable, it is intended for use in controlled repository environments. Always inspect the generated code before committing to ensure business logic remains intact.