Test automation pyramid in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the layers of the Test Automation Pyramid

Which layer of the Test Automation Pyramid typically contains the most tests and runs the fastest?

A Integration tests

B Manual tests

C End-to-end tests

D Unit tests

💡 Hint

Think about which tests check small pieces of code and run quickly.

Unit tests are at the bottom of the pyramid, are the most numerous, and run the fastest because they test small parts of the code in isolation.

🧠 Conceptual

intermediate

Purpose of integration tests in the Test Automation Pyramid

What is the main role of integration tests in the Test Automation Pyramid?

A Test individual functions in isolation

B Test how different modules work together

C Test the entire application from the user interface

D Test performance under heavy load

💡 Hint

Integration tests check connections between parts, not just one part alone.

Integration tests verify that different modules or components work together correctly, which is the middle layer of the pyramid.

❓ Predict Output

advanced

Test execution order in the Test Automation Pyramid

Given this test suite execution order, which layer is being tested first?

Testing Fundamentals

def run_tests():
    print('Running unit tests')
    print('Running integration tests')
    print('Running end-to-end tests')

run_tests()

A Unit tests

B Integration tests

C End-to-end tests

D Manual tests

💡 Hint

Look at the first print statement inside the function.

The first print statement shows 'Running unit tests', indicating unit tests run first in the suite.

❓ assertion

advanced

Correct assertion for verifying a unit test result

Which assertion correctly checks that a function add(a, b) returns 5 when called with 2 and 3?

Testing Fundamentals

def add(a, b):
    return a + b

A assert add(2, 3) != 5

B assert add(2, 3) = 5

C assert add(2, 3) == 5

D assert add(2, 3) > 5

💡 Hint

Remember the syntax for equality comparison in assertions.

Option C uses the correct syntax and logic to assert the function returns 5.

❓ framework

expert

Choosing the best test type for fast feedback in CI/CD pipeline

In a continuous integration pipeline, which test type from the Test Automation Pyramid should run first to provide the fastest feedback?

A Unit tests that verify small code parts

B Integration tests that check module interactions

C End-to-end tests that simulate user actions

D Manual exploratory tests

💡 Hint

Think about which tests are fastest and easiest to run automatically.

Unit tests run quickly and provide immediate feedback, making them ideal for early CI pipeline stages.

Practice

1. What is the main idea behind the test automation pyramid?

easy

A. Write mostly UI tests because they cover all features

B. Write many fast unit tests, fewer integration tests, and few slow UI tests

C. Write only manual tests to save automation effort

D. Write equal numbers of unit, integration, and UI tests

Solution

1. Step 1: Understand test types and speed

   Unit tests are fast and cheap, integration tests are slower, UI tests are slowest and costly.

2. Step 2: Apply pyramid principle

   The pyramid suggests many unit tests, fewer integration tests, and few UI tests to catch bugs early and keep tests efficient.

3. Final Answer:

   Write many fast unit tests, fewer integration tests, and few slow UI tests -> Option B

4. Quick Check:

   Test automation pyramid = many unit, fewer integration, few UI tests [OK]

Hint: Remember: fast tests at bottom, slow tests at top [OK]

Common Mistakes:

• Thinking UI tests should be the majority
• Believing manual tests replace automation
• Assuming all test types should be equal

2. Which of the following correctly orders test types from fastest to slowest in the test automation pyramid?

easy

A. UI tests, integration tests, unit tests

B. Integration tests, unit tests, UI tests

C. Integration tests, UI tests, unit tests

D. Unit tests, integration tests, UI tests

Solution

1. Step 1: Recall test speed hierarchy

   Unit tests run fastest because they test small code parts, integration tests are slower, UI tests are slowest due to full system interaction.

2. Step 2: Match order from fastest to slowest

   The correct order is unit tests first, then integration tests, then UI tests last.

3. Final Answer:

   Unit tests, integration tests, UI tests -> Option D

4. Quick Check:

   Speed order = unit < integration < UI [OK]

Hint: Fastest tests are smallest scope: unit first [OK]

Common Mistakes:

• Confusing UI tests as fastest
• Mixing integration and unit test order
• Ignoring test execution speed differences

3. Consider this test suite distribution: 100 unit tests, 30 integration tests, and 5 UI tests. Which statement best describes this setup according to the test automation pyramid?

medium

A. It has too few integration tests compared to UI tests

B. It has too many UI tests compared to unit tests

C. It follows the pyramid by having many unit tests and few UI tests

D. It violates the pyramid by having equal test counts

Solution

1. Step 1: Analyze test counts

   There are many unit tests (100), fewer integration tests (30), and very few UI tests (5).

2. Step 2: Compare with pyramid principle

   The pyramid recommends many unit tests, fewer integration tests, and few UI tests, matching this distribution.

3. Final Answer:

   It follows the pyramid by having many unit tests and few UI tests -> Option C

4. Quick Check:

   Test counts match pyramid shape [OK]

Hint: More unit tests, less UI tests = pyramid shape [OK]

Common Mistakes:

• Thinking 5 UI tests is too many
• Confusing integration test count importance
• Assuming equal test numbers are correct

4. A team wrote mostly UI tests and very few unit tests. What is the main problem with this approach according to the test automation pyramid?

medium

A. UI tests are slow and costly, causing slow feedback and maintenance issues

B. Unit tests are unnecessary if UI tests exist

C. Integration tests will automatically cover all bugs

D. Manual testing is better than UI tests

Solution

1. Step 1: Understand test cost and speed

   UI tests are slow to run and expensive to maintain compared to unit tests.

2. Step 2: Identify pyramid violation

   Having mostly UI tests means slow feedback and higher maintenance, which the pyramid warns against.

3. Final Answer:

   UI tests are slow and costly, causing slow feedback and maintenance issues -> Option A

4. Quick Check:

   Too many UI tests = slow, costly [OK]

Hint: Too many UI tests slow feedback [OK]

Common Mistakes:

• Ignoring unit test importance
• Assuming integration tests cover all bugs
• Confusing manual and automated UI tests

5. You want to improve your test suite following the test automation pyramid. Currently, you have 20 UI tests, 50 integration tests, and 10 unit tests. What is the best action to align with the pyramid?

hard

A. Increase unit tests significantly, reduce UI tests, and keep integration tests moderate

B. Increase UI tests to cover more features, keep others same

C. Remove unit tests and focus on integration and UI tests

D. Keep all test counts the same but run UI tests more often

Solution

1. Step 1: Analyze current test distribution

   There are few unit tests (10), many integration tests (50), and many UI tests (20), which is opposite of pyramid advice.

2. Step 2: Apply pyramid principle for improvement

   The pyramid suggests many unit tests, fewer integration tests, and few UI tests to catch bugs early and keep tests efficient.

3. Final Answer:

   Increase unit tests significantly, reduce UI tests, and keep integration tests moderate -> Option A

4. Quick Check:

   More unit, fewer UI tests = pyramid aligned [OK]

Hint: Boost unit tests, cut UI tests for pyramid fit [OK]

Common Mistakes:

• Adding more UI tests instead of unit tests
• Removing unit tests thinking they are less useful
• Ignoring test speed and cost differences