Testing Pyramid

Agile Engineering

Testing Pyramid

Balance the Test Pyramid poster. Test Pyramid provides a simple overview of how to balance the testing.

Read more

Get PDF

Tags

Agile Agile testing pyramid E2E E2E test End-to-end test image Integration Integration test Service test Software Software development Software engineering Software testing Software testing pyramid test Test automation pyramid test pyramid Testing Testing pyramid ui UI test Unit test User Interface User Interface test

Article

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.

Resources

martinfowler.com martinfowler.com browserstack.com dev.to agilenutshell.com automationpanda.com

Similar posters

Eisenhower Matrix

Eisenhower Matrix The Eisenhower Matrix, also known as the Urgent-Important Matrix, is a tool for organizing tasks by their urgency and importance to improve productivity and decision-making. It divides tasks into four quadrants based on these criteria. Do Important and Urgent Tasks in this quadrant require immediate attention and are essential to your goals. These are often...

Maker's vs Manager's schedule

Maker's vs Manager's schedule The differences between a maker’s and a manager’s schedules stem from their respective workflows’ distinct nature. Makers rely on uninterrupted time blocks to tackle complex, creative problems requiring deep focus and sustained attention. Managers need flexibility to oversee multiple responsibilities, make decisions, and collaborate effectively across teams. As such, it is essential to thoughtfully assess...

Mission Statement

Mission Statement Long-term organization purpose, values and objectives. It should describe why it matters. This way it contributes to identity creation.

Value Stream Mapping

Value Stream Mapping The Value Stream Mapping is a Lean technique for managing flow and improving processes allowing to track the flow through a process.

Minto Pyramid The Minto Pyramid Principle, a communication framework, advocates for a top-down approach to convey messages effectively

Spotify Health Check

Spotify Health Check The Spotify Health Check is a workshop, where teams assess their project and collaboration using 11 dimensions.

Maslow's Hierarchy Of Needs

Maslow's Hierarchy Of Needs Maslow's hierarchy of needs links basic human needs and desires, emphasizing that survival needs must be met before higher needs.

RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.

CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.

STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.