Test Pyramid
Status: 🌱
Motivation
Balance test speed, confidence, and maintenance effort by distributing coverage across layers.
Starter Points
- Keep most coverage in fast deterministic tests for backend domain logic and core frontend behavior.
- Use integration tests to validate contracts at real boundaries: persistence layer, messaging, and API adapters.
- Reserve end-to-end tests for a small number of critical user journeys.
- Keep contract tests between services to prevent integration drift without full environment orchestration.
- Reassess pyramid shape when test runtime or flaky rates increase.