Testing pyramid

As explained in Think Like a Software Engineering Manager

The testing pyramid is a test-suite design framework that emphasizes an appropriate distribution of automated tests across testing levels.

The testing pyramid is a framework for designing an automated test suite across three levels: unit testing at the base, integration testing in the middle, and end-to-end testing at the top. It supports regression testing and helps teams protect changes before they reach users. section 12.2.2

Use the pyramid to make testing repeatable and part of everyday delivery:

• Automate test cases so they can be rerun with minimal manual intervention. section 12.2.2
• Run tests through continuous integration tools with each code commit. section 12.2.2
• Treat testing as a safeguard and quality measure before changes reach users. section 12.2.2

The test automation pyramid helps the engineering team produce high-quality software. It works at three levels: unit testing (base step), integration testing (middle step)m and end-to-end testing (top).

Inspect the three-level pyramid: unit testing forms the base, integration testing the middle, and end-to-end testing the top. section 12.2.2

How Think Like a Software Engineering Manager covers it

How deep it goes

Defines three testing levels and their pyramid positions, but does not provide implementation details or distribution ratios.

Examples

Uses a three-level pyramid figure, commit-triggered tests, and Netflix Chaos Monkey as testing-automation examples.

What you can do after

Apply it by building repeatable automated tests and integrating them into the development workflow.

How it connects

Connects unit testing, integration testing, end-to-end testing, regression testing, continuous integration, and automation testing.

liveBookmanning.com

Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Unit Testing Principles, Practices, and PatternsThe Test Pyramid is a testing strategy that recommends a relative distribution of unit, integration, and end-to-end tests, with more tests in lower layers.
• 

  liveBookmanning.com
  Contract Testing in ActionThe test automation pyramid is a model that recommends distributing automated tests across unit, integration, and end-to-end layers, with fewer tests at slower and more expensive higher layers.
• 

  liveBookmanning.com
  Shipping Go: Develop, deliver, discuss, design, and go againA testing pyramid is a testing strategy with many fast unit tests at the base and progressively fewer broader, more expensive tests above them.
• 

  liveBookmanning.com
  Django in ActionA testing pyramid is a model that organizes software tests into levels based on scope, speed, and execution cost.
• 

  liveBookmanning.com
  Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and TerraformThe testing pyramid is a model that organizes tests into layers, with broader and generally slower tests placed above narrower and generally faster tests.
• 

  liveBookmanning.com
  Build Financial Software with Generative AI (From Scratch)A testing pyramid is a model that organizes software tests by scope, with numerous fast isolated tests at the base and fewer slower broader tests toward the top.
• 

  liveBookmanning.com
  gRPC Microservices in GoThe testing pyramid is a test-distribution model that places isolated unit tests below integration tests and end-to-end tests, with progressively fewer tests and greater execution cost at higher levels.

Compare how 8 books explain testing pyramid →

Related concepts

• testhas part · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
• integration testhas part · An integration test evaluates whether multiple software components, or a component and an external dependency, interact and behave correctly together.
• end-to-end testinghas part · End-to-end testing evaluates a complete system workflow across integrated components, from an external or user-relevant input to an observable outcome.
• unit testhas part · A unit test is a test that evaluates the behavior of a small, isolated unit of software against expected behavior.
• acceptance testinghas part · Acceptance testing evaluates whether a system or software satisfies specified user, business, or other stakeholder requirements and is acceptable for its intended purpose.

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.