What problem does it solve?
Playwright test suites often become flaky, slow, and hard to maintain due to brittle selectors, poor waits/assertions, missing isolation, and weak debugging workflows.
Core Features & Use Cases
- Test authoring guidance: Build consistent E2E, component, API, GraphQL, and visual regression tests with strong patterns for structure and page object model usage.
- Stability and maintainability: Reduce flakiness with correct locator strategy, waiting/assertion discipline, and fixture-based setup/teardown to prevent state leakage.
- Debugging and edge-case coverage: Diagnose timeouts, race conditions, selector issues, and console/JS errors while validating error states like auth/network/offline scenarios and complex multi-user flows.
- Configuration and CI integration: Configure Playwright projects and set up CI/CD (including GitHub/GitLab and container options) for dependable execution in pipelines.
Quick Start
Use the Playwright Best Practices skill to review your existing Playwright suite and recommend concrete changes to eliminate flakiness and improve test structure, locators, waits, and debugging.