Why different testing levels catch different bugs in Testing Fundamentals - Test Execution Impact

Test Overview

This test simulates how different testing levels (unit, integration, system) catch different types of bugs. It verifies that bugs found at each level match the expected bug type.

Test Code - unittest

Testing Fundamentals

import unittest

class BugDetectionTest(unittest.TestCase):
    def test_unit_level_bug(self):
        bug_found = 'logic error'
        self.assertEqual(bug_found, 'logic error')

    def test_integration_level_bug(self):
        bug_found = 'interface mismatch'
        self.assertEqual(bug_found, 'interface mismatch')

    def test_system_level_bug(self):
        bug_found = 'performance issue'
        self.assertEqual(bug_found, 'performance issue')

if __name__ == '__main__':
    unittest.main()

Execution Trace - 4 Steps

Step	Action	System State	Assertion	Result
1	Test starts and runs test_unit_level_bug	Unit test simulates finding a logic error in code	Check bug_found equals 'logic error'	PASS
2	Runs test_integration_level_bug	Integration test simulates finding interface mismatch between modules	Check bug_found equals 'interface mismatch'	PASS
3	Runs test_system_level_bug	System test simulates finding performance issue in full system	Check bug_found equals 'performance issue'	PASS
4	All tests complete	All bug types correctly detected at their testing levels	—	PASS

Failure Scenario

Failing Condition: Bug type does not match expected value at a testing level

Execution Trace Quiz - 3 Questions

Which testing level is best at catching logic errors inside a single function?

A Unit testing

B Integration testing

C System testing

D Acceptance testing

Key Result

Different testing levels focus on different parts of the software, so they catch different types of bugs. Unit tests catch small code errors, integration tests catch problems between parts, and system tests catch issues in the whole system.

Practice

1. Which testing level focuses on checking individual parts of the software separately?

easy

A. Acceptance Testing

B. System Testing

C. Integration Testing

D. Unit Testing

Solution

1. Step 1: Understand testing levels

   Unit testing checks small parts or units of code individually.

2. Step 2: Compare options to definitions

   System testing checks the whole system, integration testing checks combined parts, acceptance testing checks if requirements are met.

3. Final Answer:

   Unit Testing -> Option D

4. Quick Check:

   Individual parts = Unit Testing [OK]

Hint: Unit testing tests small parts alone [OK]

Common Mistakes:

• Confusing integration testing with unit testing
• Thinking system testing tests parts separately
• Mixing acceptance testing with unit testing

2. Which of the following is the correct order of testing levels from smallest to largest scope?

easy

A. System Testing -> Integration Testing -> Unit Testing

B. Unit Testing -> Integration Testing -> System Testing

C. Integration Testing -> Unit Testing -> System Testing

D. Acceptance Testing -> System Testing -> Unit Testing

Solution

1. Step 1: Identify scope sizes

   Unit testing checks smallest parts, integration testing checks combined parts, system testing checks whole system.

2. Step 2: Arrange from smallest to largest

   Correct order is Unit Testing, then Integration Testing, then System Testing.

3. Final Answer:

   Unit Testing -> Integration Testing -> System Testing -> Option B

4. Quick Check:

   Smallest to largest = A [OK]

Hint: Remember: Unit, Integration, System order [OK]

Common Mistakes:

• Reversing the order of testing levels
• Confusing integration with system testing
• Including acceptance testing in the wrong place

3. Consider this scenario: A bug appears only when two modules interact but not in individual modules. Which testing level is most likely to catch this bug?

medium

A. Integration Testing

B. Unit Testing

C. System Testing

D. Acceptance Testing

Solution

1. Step 1: Analyze bug context

   The bug appears only when two modules interact, so it is related to combined parts.

2. Step 2: Match testing level to bug type

   Integration testing focuses on testing combined modules and their interactions.

3. Final Answer:

   Integration Testing -> Option A

4. Quick Check:

   Bug in combined modules = Integration Testing [OK]

Hint: Bugs in combined parts? Think Integration Testing [OK]

Common Mistakes:

• Choosing unit testing for interaction bugs
• Confusing system testing with integration testing
• Assuming acceptance testing finds module interaction bugs

4. A tester wrote a test that checks the entire software system but missed testing how modules work together. What testing level did they likely skip?

medium

A. Integration Testing

B. Unit Testing

C. Acceptance Testing

D. System Testing

Solution

1. Step 1: Understand the test scope

   The tester tested the whole system but did not check module interactions.

2. Step 2: Identify missing testing level

   Integration testing specifically checks how modules work together, so it was likely skipped.

3. Final Answer:

   Integration Testing -> Option A

4. Quick Check:

   Missed module interaction = Integration Testing [OK]

Hint: Check module interactions with Integration Testing [OK]

Common Mistakes:

• Confusing system testing with integration testing
• Assuming unit testing covers module interactions
• Thinking acceptance testing covers module integration

5. A software project has a bug that only appears when the full system runs with real user data, but not during unit or integration tests. Which testing level is best suited to find this bug?

hard

A. Unit Testing

B. Integration Testing

C. System Testing

D. Acceptance Testing

Solution

1. Step 1: Analyze bug conditions

   The bug appears only when the full system runs with real user data, not in smaller tests.

2. Step 2: Match testing level to scenario

   System testing checks the entire system working together, often with realistic data, so it is best to find such bugs.

3. Final Answer:

   System Testing -> Option C

4. Quick Check:

   Full system with real data = System Testing [OK]

Hint: Full system bugs? Use System Testing [OK]

Common Mistakes:

• Choosing unit or integration testing for full system bugs
• Confusing acceptance testing with system testing
• Ignoring the importance of real user data in tests