What problem does it solve?
Use when writing Playwright E2E tests for new or modified features, investigating failing
tests, assessing test coverage gaps, designing a test strategy for a feature, setting up
test infrastructure, or verifying that implemented behavior matches requirements.
Core Features & Use Cases
- Ground tests in requirements: Before creating or updating E2E tests, reference relevant requirements (e.g., FR-XXX) in PRD.md and trace critical paths.
- Follow testing conventions: Apply Playwright E2E conventions (file structure, naming, and page object models) and use fixtures, storage state caching, and test.use overrides to reduce setup time and flakiness.
- Anti-flakiness and optimization: Implement deterministic data, wait for real conditions, and use CI-friendly patterns like test retries and artifact uploads.
- Accessibility and tooling: Integrate accessibility checks and network-mocking strategies to ensure reliable, compliant tests.
- CI & quality culture: Emphasize coverage philosophy, test reviews, and anti-pattern avoidance to improve reliability and maintainability.
Quick Start
Follow the protocol to create a Playwright E2E test strategy for a new feature.