test pyramid

A guide for balancing a test suite: many fast unit tests, fewer integration tests and a small number of end-to-end tests.

In more detail

It is a conversation about feedback speed, diagnosis and risk, not a fixed ratio for every repository. Choose tests from risk, and let production incidents add or improve tests.

Example

In this course: Mike Cohn described it and Martin Fowler popularised it. The height stands for cost: tests near the top are slower, need more of the system running and fail for more reasons unrelated to your change. It is a default shape, not a quota, and the right shape depends on your architecture and risks.

Related terms

Taught in

References

Certification courses