End-to-End Playwright Testing
Creates robust end-to-end Playwright tests that simulate real user behavior through a structured, three-phase workflow.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Generates tests that simulate real user journeys by interacting with the DOM.
- Provides an automated test healing strategy to fix failures caused by UI changes.
- Enforces a mandatory three-phase workflow: Plan, Generate, and Heal.
- Prioritizes accessible locators (e.g., getByRole, getByLabel) for robust implementation.
- Distinguishes between test setup (where API helpers are allowed) and the core test action (where UI interaction is mandatory).
Use cases
- Debugging and fixing a failing Playwright test in a CI/CD pipeline.
- Creating a new end-to-end test suite for a feature.
- Refactoring existing tests to better reflect user workflows and improve reliability.
FAQ
How does this skill improve my testing workflow?
It introduces a systematic process that reduces flaky tests. By prioritizing user-like DOM interactions over API shortcuts and providing an automated 'healing' phase, it saves significant time on writing, debugging, and maintaining your E2E test suite.
When should I use the End-to-End Playwright Testing skill?
Use this skill whenever you need to create, modify, or debug end-to-end tests, especially when working with the Playwright framework or in an `e2e/` directory. It ensures tests are realistic, robust, and maintainable.
Why does this skill focus on UI interaction over API calls?
To ensure tests are authentic, the skill avoids API shortcuts for the main test action. This forces the test to use the UI just like a real user would, which is crucial for catching UI-specific bugs that API-level tests would miss.
What does this Claude Code Skill do?
This skill guides Claude through a strict, three-phase workflow (Plan, Generate, Heal) to create, implement, and automatically fix end-to-end Playwright tests that accurately simulate real user interactions with your application's UI.
What are the core capabilities of this skill?
It enforces a structured workflow with three dedicated phases: a planner for defining user journeys, a generator for writing accessible test code using best practices, and a healer for automatically fixing failures caused by UI changes.
Related skills
UI Testing
Guides the development of robust UI tests using Cypress and Testing Library, covering component tests, end-to-end flows, and accessibility.
Security Testing1012 ptsWeb Application Testing
Builds and debugs web application features through a structured, iterative testing process using Playwright.
Security Testing6912 ptsTesting Workflow
Executes comprehensive test suites including unit, integration, E2E, and mutation tests to validate code changes and ensure quality.
Security Testing12 pts