domains / families / software-engineering / e2e-testing-patterns

e2e-testing-patterns

combined

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. Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.

When to use

• 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

When not to use

• You only need unit or integration tests
• The environment cannot support stable UI automation
• You cannot provision safe test accounts or data
• A mocked backend or payment provider proves only the mocked boundary; retain separate real integration checks.
• Automated accessibility scans miss interaction and assistive-technology problems.
• Retries, larger timeouts and updated snapshots can hide regressions; preserve first-failure evidence.
• Browser tooling cannot validate a locked or unavailable interactive environment. Report that gap and continue independent tests.

Skill page

Conflict

The sickn33 copy is a superset of the rmyndharis copy. It contains all the same sections but adds a 'Worked example', 'Inputs and prerequisites', and 'Limitations' sections. It also modifies step 3 of the instructions to be more specific about retries ('diagnose retries rather than counting a retry as an ordinary pass'). Because the sickn33 copy contains material steps and constraints the rmyndharis copy lacks, and the rmyndharis copy is a shortened version, crowning one would hide the more complete alternative. However, since they are essentially the same skill with one being a more detailed version, 'combine' is the correct decision to ensure the most complete instruction set is used, or to acknowledge the discrepancy in detail level.