Test automation pyramid in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Test Automation Pyramid?

The Test Automation Pyramid is a model that shows how to organize automated tests. It suggests having many small, fast unit tests at the bottom, fewer integration tests in the middle, and even fewer slow, expensive UI tests at the top.

beginner

Why should there be more unit tests than UI tests in the Test Automation Pyramid?

Unit tests are fast, cheap, and easy to maintain. UI tests are slower, more fragile, and costly. Having more unit tests helps catch bugs early and keeps tests running quickly.

beginner

Name the three layers of the Test Automation Pyramid from bottom to top.

1. Unit Tests (bottom) - test small pieces of code 2. Integration Tests (middle) - test how parts work together 3. UI/End-to-End Tests (top) - test the whole system from the user's view

intermediate

What is a key benefit of following the Test Automation Pyramid?

It helps create a balanced test suite that is fast, reliable, and cost-effective by focusing on many small tests and fewer slow, complex tests.

beginner

Give a real-life example to explain the Test Automation Pyramid.

Think of checking a car before a trip: you check many small parts like tires and oil (unit tests), then test how the engine and brakes work together (integration tests), and finally take the car for a short drive to see if everything works as a whole (UI tests).

Which layer of the Test Automation Pyramid should have the most tests?

A Manual Tests

B Integration Tests

C Unit Tests

D UI Tests

Unit tests are the foundation and should be the most numerous because they are fast and cheap.

Why are UI tests placed at the top of the Test Automation Pyramid?

A They are the most expensive and slowest tests

B They test small pieces of code

C They are the fastest tests

D They do not require maintenance

UI tests are slow and costly, so fewer of them are recommended.

What is the main focus of integration tests in the pyramid?

A Testing how different parts work together

B Testing individual functions

C Testing the user interface

D Testing performance only

Integration tests check if different parts of the system work well together.

What happens if you have too many UI tests and not enough unit tests?

A Tests run faster

B Tests become slow and fragile

C You catch bugs earlier

D Tests require less maintenance

Too many UI tests slow down testing and are more likely to break.

Which of these is NOT a benefit of following the Test Automation Pyramid?

A Lower maintenance cost

B Balanced test coverage

C Faster test execution

D More manual testing

The pyramid encourages automated tests, not more manual testing.

Explain the Test Automation Pyramid and why it is important.

Think about test speed, cost, and reliability.

Describe a real-life example that helps you understand the Test Automation Pyramid.

Use something like checking a car or cooking a meal.