E2e Testing Patterns

1---
2name: e2e-testing-patterns
3description: 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.
4---
5 
6# E2E Testing Patterns
7 
8Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.
9 
10## Use this skill when
11 
12- Implementing end-to-end test automation
13- Debugging flaky or unreliable tests
14- Testing critical user workflows
15- Setting up CI/CD test pipelines
16- Testing across multiple browsers
17- Validating accessibility requirements
18- Testing responsive designs
19- Establishing E2E testing standards
20 
21## Do not use this skill when
22 
23- You only need unit or integration tests
24- The environment cannot support stable UI automation
25- You cannot provision safe test accounts or data
26 
27## Instructions
28 
291. Identify critical user journeys and success criteria.
302. Build stable selectors and test data strategies.
313. Implement tests with retries, tracing, and isolation.
324. Run in CI with parallelization and artifact capture.
33 
34## Safety
35 
36- Avoid running destructive tests against production.
37- Use dedicated test data and scrub sensitive output.
38 
39## Resources
40 
41- `resources/implementation-playbook.md` for detailed E2E patterns and templates.
42