What problem does it solve?
Prevents costly regressions by verifying that the most important end-to-end user journeys work correctly across authentication, authorization, multi-step workflows, and high-risk failure paths without making CI slow or flaky.
Core Features & Use Cases
- Narrow, stable E2E coverage: Focuses on a small set of critical journeys that must pass quickly (targeting under 10 minutes).
- Deterministic testing practices: Enforces semantic selectors (ARIA-first or data-testid only when needed), per-test isolated data, and event-based waits instead of arbitrary time delays.
- Business-outcome assertions: Requires user-visible confirmations plus durable side effects (e.g., created records, sent emails, or emitted events) to prove real functionality.
- Auth and permission safety: Mandates coverage for valid login, invalid credentials, session expiry, and permission-denied flows.
- Debuggable CI failures: Requires Playwright traces, screenshots, and optionally video on failure plus a flake quarantine policy.
Quick Start
Use the e2e-testing capability when a change touches login, permissions, checkout/payment confirmation, destructive actions, or other multi-step high-risk journeys that must be proven through the assembled system with isolated test data and business-outcome assertions.
