Testing pyramid

As explained in Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

The testing pyramid is a model that organizes tests into layers, with broader and generally slower tests placed above narrower and generally faster tests.

The testing pyramid balances test coverage and feedback speed: keep many fast unit tests at the base, fewer integration tests above them, and still fewer end-to-end tests at the top. section 9.4

Use each layer for a different scope:

• Unit tests exercise a small function or code unit in isolation, often with mocked dependencies. section 9.12
• Integration tests exercise a whole microservice through its normal interface, such as HTTP requests or messages. section 9.12
• End-to-end tests exercise groups of microservices or the full application, including the frontend. section 9.4

A practical microservices stack

Run unit and integration tests with Jest, use its --watch or --watchAll flags for rapid feedback, start a cut-down application with Docker Compose, and drive the frontend with Playwright for end-to-end tests. Connect the suite to CI/CD so failures warn before production. section 9.12 section 9.4

Figure 9.1 The testing pyramid indicates the relative amounts of each type of test we should have.

Use the diagram to compare the relative amounts of unit, integration, and end-to-end tests in a suite. section 9.4

How Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform covers it

How deep it goes

Defines three testing levels, their relative quantities, interfaces, and tools, but does not detail test implementation beyond these practices.

Examples

Uses isolated functions, whole microservices, HTTP or message interfaces, and a Docker Compose application tested through a frontend.

What it assumes

Assumes an automated-testing context while defining unit, integration, and end-to-end testing from their basic purposes.

What you can do after

Apply via Jest, Docker Compose, Playwright, and CI/CD to build layered automated tests with rapid local feedback.

How it connects

Connects unit testing, integration testing, end-to-end testing, mocking, microservices, Docker Compose, Jest, Playwright, and CI/CD.

liveBookmanning.com

Read Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform 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
  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
  Think Like a Software Engineering ManagerThe testing pyramid is a test-suite design framework that emphasizes an appropriate distribution of automated tests across testing levels.
• 

  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 Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform. The section links point to the parts of the book it draws on.