End-to-End Testing
Quick Reference
What & Why
Definition
>= 50% of critical user journeys covered by automated E2E tests (Playwright, Cypress).
Business Value
Catches 70% of bugs before production deployment and reduces QA cycle time by 50% through comprehensive automated test coverage Achieving >= 50% critical journeys have E2E tests is a key milestone toward this goal.
Context
This capability is part of the Foundation milestone's focus on establish baseline practices (testable, releasable, monitorable). Essential for teams targeting CFR, LT improvements.
Success Criteria
Target
>= 50% critical journeys have E2E tests
Measurement
E2E test suite coverage mapping to user journeys
Evidence
- E2E test code
- Test execution videos
- Journey coverage matrix
In Practice
Real-World Implementation
Teams identify top 10 critical journeys, automate with Playwright, run in CI on every PR to main, run nightly on staging.
Concrete Example
Implementation Guide
Implementation Steps
Follow the measurement approach: E2E test suite coverage mapping to user journeys
For detailed step-by-step guidance, refer to the Testing Strategy & Quality Gates Implementation Kit.
Resources
Implementation Kit
Testing Strategy & Quality Gates KitTemplates
Browse all templatesRelated Resources
View learning pathsRelated Capabilities
Enables
What this unlocks
Complementary
Often adopted together, from the Testing Strategy & Quality Gates epic
Troubleshooting & FAQs
Common Issues
Issue: Target metric not improving
Solution: Verify measurement is accurate, check if prerequisites are fully implemented, review evidence artifacts for completeness
Issue: Team resistance to adoption
Solution: Start with pilot team, demonstrate value with metrics, provide training and support during transition
Issue: Inconsistent implementation across teams
Solution: Create shared templates and guidelines, establish regular sync meetings, use automation to enforce standards
Frequently Asked Questions
Can we implement this before completing prerequisites?
While possible, it's not recommended. Prerequisites ensure foundational practices are in place, making this capability more effective and easier to adopt.
How long does implementation typically take?
Most capabilities can be implemented within 90 days when tackled as part of the Foundation milestone. Individual timelines vary based on team size and existing practices.