Home › Key concepts › The testing pyramid

Key concept · Crawl (beginner) · the same on every platform

The testing pyramid

Many small fast tests, fewer bigger ones, a handful end to end.

What it is

Unit tests check one function in milliseconds. Integration tests check parts working together, such as code and a database. End-to-end tests check a whole journey. Most tests should be small and fast, so you run them on every change.

Why it matters

Fast tests catch most bugs before anyone else sees them.

An example

A unit test checks the discount function with 20 cases; one end-to-end test places a real order in a test environment.

The common mistake

Only end-to-end tests: slow, flaky, and they don't say where the bug is.

Where you meet it on each platform

The idea stays the same; only the product name changes.

JobAWSAzureGoogle CloudDatabricksOpen source
CI/CDevery change is tested and shipped by a pipeline, not by handGitHub Actions + CodeDeployGitHub Actions or Azure PipelinesGitHub Actions + Cloud BuildGitHub Actions + bundlesGitHub Actions

Related ideas

Where it shows up

Part of the Crawl level on these paths: Software Engineering (working together).