E2E Testing Patterns

**Quick judgment** High-quality, opinionated patterns for building robust Playwright/Cypress E2E suites. Best suited for teams doing browser-based web testing in JS/TS who want to reduce flakiness and make tests CI-friendly, not for mobile-native or non-browser systems. **Key strengths** - Strong emphasis on behavior-focused tests, critical-path coverage, and the test pyramid. - Concrete patterns: Page Object Model, fixtures for test data, smart waits, network mocking, and selector strategy. - Includes visual regression, accessibility testing, debugging workflows, and CI (GitHub Actions) integration examples. - Encourages best practices: independent tests, no fixed timeouts, stable selectors, and immediate flaky test remediation. **Risks / limitations** - Tooling-specific: heavily focused on Playwright and Cypress in a Node/TypeScript ecosystem; less applicable to teams using other E2E frameworks (e.g., Selenium, WebdriverIO) or non-JS stacks. - Opinionated patterns (e.g., strong preference against CSS/DOM-based selectors, heavy mocking of external services) may conflict with existing team conventions or observability needs. - Does not cover non-web E2E scenarios (mobile-native, desktop apps, pure API flows) and offers limited guidance on cross-org governance (test ownership, coverage metrics, etc.). **Recommended scenarios** - Bootstrapping or standardizing a Playwright/Cypress E2E suite for a modern web app. - Cleaning up a flaky, slow suite by introducing deterministic waits, fixtures, and stable selectors. - Training developers/QA on how to choose what belongs in E2E vs unit/integration tests. - Integrating E2E checks into CI/CD with actionable failure diagnostics (traces, screenshots, reports).