What the pyramid means
The pyramid encourages teams to keep most automated validation at lower technical layers and use fewer expensive end-to-end tests.
E2E
/ \
UI Mobile
/ \
API / Integration
/ \
Component / Contract
\ /
Unit Tests
Why lower-level tests help
- Fast execution
- Easier diagnosis
- Lower setup cost
- Less environment dependency
- More deterministic results
- Better developer feedback
Why higher levels still matter
Lower-level tests cannot prove that deployed integrations, browser behaviour, configuration, and whole user journeys work together.
The pyramid is about balance—not eliminating UI or E2E testing.
Do not use rigid percentages
There is no universal 70/20/10 rule. Mobile apps, APIs, data platforms, SaaS implementations, and embedded systems naturally produce different shapes.
Lowest effective layer
| Risk | Likely layer |
|---|---|
| Calculation | Unit/component |
| API schema | Contract/API |
| Database mapping | Integration/data |
| Critical checkout | Selected E2E |
| Responsive layout | UI/visual |
Ask: what is the lowest layer that can validate this risk with sufficient confidence?