| name | e2e-testing-patterns |
| description | Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards. |
| license | MIT |
| metadata | {"version":"1.0.0","domain":"frontend","triggers":"E2E testing, Playwright, Cypress, end-to-end, test automation, flaky tests","role":"specialist","scope":"implementation","output-format":"code","related-skills":"test-driven-development, unit-testing-test-generate"} |
E2E Testing Patterns
Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.
Use this skill when
- Implementing end-to-end test automation
- Debugging flaky or unreliable tests
- Testing critical user workflows
- Setting up CI/CD test pipelines
- Testing across multiple browsers
- Validating accessibility requirements
- Testing responsive designs
- Establishing E2E testing standards
Do not use this skill when
- You only need unit or integration tests
- The environment cannot support stable UI automation
- You cannot provision safe test accounts or data
Instructions
- Identify critical user journeys and success criteria.
- Build stable selectors and test data strategies.
- Implement tests with retries, tracing, and isolation.
- Run in CI with parallelization and artifact capture.
Safety
- Avoid running destructive tests against production.
- Use dedicated test data and scrub sensitive output.
Resources
resources/implementation-playbook.md for detailed E2E patterns and templates.
