Test Pyramid
An automated testing hierarchy model proposed by Mike Cohn in 2009, comprising unit tests at the base, integration tests in the middle, and end-to-end tests at the top. It is a foundational framework for guiding CI testing strategy.
Core Facts
The testing pyramid was proposed by Google engineer Mike Cohn, with unit tests, integration tests, and E2E tests arranged from the bottom to the top.
The bottom layer of the testing pyramid consists of unit tests (millisecond-level, most numerous), the middle layer of integration tests (second-level), and the top layer of end-to-end tests (minute-level, fewest in number).
Timeline (last 90 days)
The test pyramid consensus holds that there should be many unit tests, a moderate number of integration tests, and a small number of E2E tests, because E2E maintenance costs rise nonlinearly with quantity.
The Agent testing pyramid recommended by the author is: run schema validation on every submission at the bottom layer, run guardrail assertions on 20+ diverse inputs nightly at the middle layer, and conduct LLM-as-Judge evaluation on a benchmark set weekly at the top layer.
The core principle of the testing pyramid is to test at the lowest level that provides sufficient confidence.
The testing pyramid advocates for a large number of fast unit tests at the bottom, fewer integration tests in the middle, and a small set of end-to-end tests at the top.
The testing pyramid was formally proposed by Mike Cohn in his 2009 book "Succeeding with Agile".
Classic engineering practices such as CI/CD, code review, branching strategies, and the test pyramid are all built on the assumption that humans are the primary executors.
The test pyramid was proposed by Mike Cohn in 2009.
The bottom layer of the testing pyramid consists of unit tests (millisecond-level, most numerous), the middle layer of integration tests (second-level), and the top layer of end-to-end tests (minute-level, fewest in number).
All Facts (10)
The testing pyramid was proposed by Google engineer Mike Cohn, with unit tests, integration tests, and E2E tests arranged from the bottom to the top.
80%VerifiedThe bottom layer of the testing pyramid consists of unit tests (millisecond-level, most numerous), the middle layer of integration tests (second-level), and the top layer of end-to-end tests (minute-level, fewest in number).
65%UnverifiedThe test pyramid concept was proposed by Mike Cohn in 2009.
60%UnverifiedThe test pyramid consensus holds that there should be many unit tests, a moderate number of integration tests, and a small number of E2E tests, because E2E maintenance costs rise nonlinearly with quantity.
50%UnverifiedThe Agent testing pyramid recommended by the author is: run schema validation on every submission at the bottom layer, run guardrail assertions on 20+ diverse inputs nightly at the middle layer, and conduct LLM-as-Judge evaluation on a benchmark set weekly at the top layer.
50%UnverifiedThe testing pyramid advocates for a large number of fast unit tests at the bottom, fewer integration tests in the middle, and a small set of end-to-end tests at the top.
50%UnverifiedThe core principle of the testing pyramid is to test at the lowest level that provides sufficient confidence.
50%UnverifiedThe testing pyramid was formally proposed by Mike Cohn in his 2009 book "Succeeding with Agile".
50%UnverifiedClassic engineering practices such as CI/CD, code review, branching strategies, and the test pyramid are all built on the assumption that humans are the primary executors.
50%UnverifiedThe test pyramid was proposed by Mike Cohn in 2009.
50%