Testing Pyramid

Balance the Test Pyramid

Unit tests

  • Testing individual components or functionalities. They are small and isolated, so every Unit test can run separately.
  • They are fast, so they can be executed often. The good practice is to execute the Unit tests with every code change.
  • They are considered the cheapest as they are easiest to maintain, they run fast and can be the first to find mistakes if used properly.
  • These are the reasons for having the highest number of Unit tests.

System / Integration tests

  • Testing the interaction between individual components of application as interactions between APIs, databases and the like. This is the reason for higher complexity than Unit tests, but they exclude the testing of the UI compared to the E2E tests.
  • They are slower compared to the unit tests as they test parts of the application interacting together.
  • The maintenance costs are higher since the different parts of the app are involved.

User Interface (UI) / End-to-end (E2E) tests

  • To ensure that the whole application works as required. User interface testing is the usual way of implementing such tests.
  • These tests take the longest time to run, which can be expensive. That is why they are not run so often compared to the previous.
  • They are the most expensive to maintain as a lot of them can be broken easily by system enhancements.

Similar posters

Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.
Little's law
Little's law Little’s Law is a theorem for queuing systems. It determines the average number of items in a stationary queuing system
User Story Creation
User Story Creation Creating a User Story is a continuous process based on the 3Cs phases, supported by INVEST, 5Ws, and the Definition of Done.
Radical Candor
Radical Candor Radical Candor is a framework describing four different behaviors. In order to become Radically Candid you need to understand all four types.
GSD / Get Stuff Done Whee
GSD / Get Stuff Done Whee Get Stuff Done Wheel is a framework for aligning and guiding the work of a team. It allows teams to deliver remarkable results more quickly
AIDA Model
AIDA Model The AIDA model is a model, where a persona moves through a series of steps to make a purchase decision, used in marketing, sales, planning...