What is the test pyramid?

The test pyramid is a strategy to keep your test suite:

• fast
• reliable
• easy to maintain

The idea: write many small unit tests, fewer integration tests, and the fewest end-to-end (E2E/UI) tests.

Diagram: Test pyramid

  graph TD
U[Many Unit Tests\nFast + Stable] --> I[Fewer Integration Tests\nMedium speed]
I --> E[Few End-to-End Tests\nSlow + Flaky]

Why this works

• Unit tests run in milliseconds → fast feedback
• Integration tests validate boundaries (DB/API/files)
• E2E tests validate realistic user workflows

Common anti-pattern

An inverted pyramid (too many UI tests):

• slow pipelines
• flaky failures
• hard debugging

Practical guidance

• Put most logic behind unit-tested functions/classes
• Use integration tests for real dependencies (DB, HTTP)
• Use a small number of E2E tests for critical paths (login, checkout)

Visualize it

The pyramid shape reflects how many tests you should have at each level - lots at the base, fewer as you go up.

  flowchart TB
U["Unit tests (many, fast)"] --> I["Integration tests (some)"]
I --> E["E2E / UI tests (few, slow)"]