Testing vs debugging distinction in Testing Fundamentals - Test Execution Compared

Test Overview

This test checks the difference between testing and debugging by simulating a simple test that finds a bug and then the debugging step to fix it. It verifies that testing detects the problem and debugging resolves it.

Test Code - unittest

Testing Fundamentals

import unittest

class Calculator:
    def add(self, a, b):
        return a + b

    def subtract(self, a, b):
        # Bug: mistakenly adds instead of subtracting
        return a + b

class TestCalculator(unittest.TestCase):
    def test_subtract(self):
        calc = Calculator()
        result = calc.subtract(5, 3)
        self.assertEqual(result, 2, "Subtract method should return difference")

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

Execution Trace - 7 Steps

Step	Action	System State	Assertion	Result
1	Test starts by importing unittest and defining Calculator class with add and subtract methods	Code loaded in memory, no errors yet	—	PASS
2	Test case TestCalculator.test_subtract is executed	Calculator instance created, subtract method called with (5,3)	Check if subtract(5,3) equals 2	FAIL
3	Test framework reports failure because subtract returned 8 instead of 2	Test report shows failure with message 'Subtract method should return difference'	AssertionError: 8 != 2	FAIL
4	Developer starts debugging by inspecting subtract method code	Code shows subtract method incorrectly adds instead of subtracting	—	PASS
5	Developer fixes subtract method to return a - b	Code updated, subtract method now correct	—	PASS
6	Test case re-run after fix	subtract(5,3) returns 2 as expected	Check if subtract(5,3) equals 2	PASS
7	Test framework reports test passed	Test report shows all tests passed	—	PASS

Failure Scenario

Failing Condition: subtract method incorrectly adds numbers instead of subtracting

Execution Trace Quiz - 3 Questions

What does the test detect in this example?

A A syntax error in the code

B A missing test case

C A bug in the subtract method

D A performance issue

Key Result

Testing helps find problems by checking expected behavior, while debugging is the process of finding and fixing the cause of those problems.

Practice

1. What is the main purpose of testing in software development?

easy

A. To find bugs by checking if the software works as expected

B. To fix the cause of bugs in the code

C. To write new features for the software

D. To design the user interface

Solution

1. Step 1: Understand the role of testing

   Testing is about running the software to check if it behaves correctly and to find any bugs.

2. Step 2: Differentiate testing from debugging

   Debugging is about finding and fixing the cause of bugs, not just finding them.

3. Final Answer:

   To find bugs by checking if the software works as expected -> Option A

4. Quick Check:

   Testing = Find bugs [OK]

Hint: Testing finds bugs; debugging fixes bugs [OK]

Common Mistakes:

• Confusing testing with fixing bugs
• Thinking testing creates new features
• Mixing testing with design tasks

2. Which of the following best describes debugging?

easy

A. Writing code to add features

B. Finding and fixing the cause of bugs

C. Running tests to find errors

D. Designing test cases

Solution

1. Step 1: Define debugging

   Debugging means investigating the cause of bugs and correcting them in the code.

2. Step 2: Compare with other options

   Running tests is testing, not debugging. Writing features and designing tests are different tasks.

3. Final Answer:

   Finding and fixing the cause of bugs -> Option B

4. Quick Check:

   Debugging = Fix bugs [OK]

Hint: Debugging fixes bugs, not just finds them [OK]

Common Mistakes:

• Confusing debugging with testing
• Thinking debugging is writing new code
• Mixing debugging with test design

3. Consider this scenario: A tester runs a test and finds the software crashes when clicking a button. What is the next step in debugging?

medium

A. Write more test cases for other buttons

B. Ignore the crash and continue testing

C. Analyze the code to find why the crash happens

D. Change the button label text

Solution

1. Step 1: Identify the testing result

   The test found a crash when clicking a button, indicating a bug.

2. Step 2: Understand debugging action

   Debugging means analyzing the code to find the cause of the crash and fix it.

3. Final Answer:

   Analyze the code to find why the crash happens -> Option C

4. Quick Check:

   Debugging = Analyze and fix bug [OK]

Hint: After finding bug, analyze code cause [OK]

Common Mistakes:

• Continuing testing without fixing bugs
• Ignoring bugs found during testing
• Changing unrelated UI elements

4. A developer writes code but the program crashes. Which step is part of debugging to fix this?

medium

A. Run tests to find if the program crashes

B. Write more features before fixing the crash

C. Ignore the crash and release the software

D. Check the error message and trace the code causing the crash

Solution

1. Step 1: Identify debugging task

   Debugging involves checking error messages and tracing code to find the cause of crashes.

2. Step 2: Eliminate incorrect options

   Running tests finds bugs but does not fix them. Writing features or ignoring crashes are wrong.

3. Final Answer:

   Check the error message and trace the code causing the crash -> Option D

4. Quick Check:

   Debugging = Trace and fix errors [OK]

Hint: Use error messages to trace bugs [OK]

Common Mistakes:

• Confusing testing with debugging
• Skipping error analysis
• Adding features before fixing bugs

5. A software tester finds a bug where the app crashes only when a specific input is given. What is the best combined approach to handle this?

hard

A. Write a test case for that input and then debug the code to fix the crash

B. Ignore the input and test other features

C. Fix the code without writing any test cases

D. Write test cases for all inputs except the problematic one

Solution

1. Step 1: Understand testing role

   Writing a test case for the specific input helps reproduce and confirm the bug.

2. Step 2: Understand debugging role

   Debugging the code to fix the crash addresses the root cause of the bug.

3. Step 3: Combine testing and debugging

   Both steps together ensure the bug is found, fixed, and verified.

4. Final Answer:

   Write a test case for that input and then debug the code to fix the crash -> Option A

5. Quick Check:

   Test to find + Debug to fix = Correct approach [OK]

Hint: Test to find bug, debug to fix bug [OK]

Common Mistakes:

• Skipping test case creation for bugs
• Fixing bugs without verifying
• Ignoring problematic inputs