Automate End-to-End Software Testing

E2E Testing Patterns builds reliable, fast, and maintainable end-to-end test suites meant to give confidence to ship quickly and catch regressions before users do. Its workflow: identify critical user journeys and success criteria, build stable selectors and test-data strategies, implement tests with retries, tracing, and isolation, and run them in CI with parallelization and artifact capture. It carries an explicit safety constraint: avoid running destructive tests against production, and use dedicated test data while scrubbing sensitive output.

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, or establishing E2E testing standards. Don't use it if you only need unit or integration tests, if the environment can't support stable UI automation, or if you can't provision safe test accounts or data. Detailed patterns and templates live in a companion resources/implementation-playbook.md file.

Input is the application's critical user journeys and a target environment (browsers, CI pipeline); output is an E2E test suite with stable selectors, retries, tracing, and test isolation, running in CI with parallelization and artifact capture for debugging failures.

Teams building or stabilizing end-to-end test suites for critical user workflows who need retries, tracing, isolation, and CI parallelization built in from the start, rather than debugging flakiness after the fact.