Loading content
The Test Pyramid describes a model for organizing tests in software development projects. It promotes a balanced distribution of unit, integration, and end-to-end tests to maximize the efficiency and effectiveness of the testing strategy.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
The test pyramid is a heuristic for balancing fast, numerous tests with fewer, slower tests at higher levels.
Mike Cohn coined the test pyramid as an image for balanced test automation. Martin Fowler made the model more widely known through his account of practical test pyramids in software development; teams have since used it to discuss test distribution and feedback speed.
Many fast unit and component tests form the broad base. Fewer integration and API tests sit above them, with a small number of slow end-to-end tests at the top. The shape is a decision heuristic: it is adapted to risks and system architecture rather than prescribing a fixed count or ratio.
A test suite combines fast feedback from lower-level tests with targeted system coverage.
Higher-level tests provide realistic confidence but usually cost more time and are more fragile.
The distribution follows risk, feedback needs and the constraints of the architecture.
The test pyramid guides decisions about test automation, feedback time and the effort invested in realistic system tests.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.