The Testing Trophy Alternative
You'll learn: How the testing trophy model shifts emphasis toward integration tests as the foundation of test suites in modern applications.
What Is the Testing Trophy?
The testing trophy is an alternative to the testing pyramid, proposed by Kent C. Dodds for modern web applications. While the pyramid emphasizes unit tests at the base, the trophy flips the emphasis: integration tests form the widest, most important layer.
The trophy has four layers from bottom to top:
- Static analysis (linting, type checking) — the base
- Unit tests — small layer
- Integration tests — the widest, most emphasized layer
- End-to-end tests — moderate presence at the top
Why Emphasize Integration Tests?
The trophy argues that integration tests provide the best return on investment for many applications because:
- They test how multiple units work together (closer to real usage)
- They catch interface mismatches and integration bugs
- They're less brittle than mocking-heavy unit tests
- They still run relatively fast compared to full E2E tests
Think of it like testing a car: unit tests check individual parts (engine, brakes), but integration tests verify that the engine connects properly to the transmission and wheels — catching issues where components meet.
When Does the Trophy Make Sense?
The trophy model works well for:
- Web applications with complex user interactions
- Systems where integration points are the riskiest areas
- Teams that struggled with brittle unit tests or over-mocking
- Codebases where business logic lives across component boundaries
Key Takeaway: The testing trophy prioritizes integration tests over unit tests, offering an alternative strategy focused on testing component interactions where many real-world bugs hide, especially in modern web applications.