Why defect tracking improves quality in Testing Fundamentals - Test Execution Impact

Test Overview

This test simulates a defect tracking process in a software project. It verifies that defects are logged correctly, assigned, fixed, and retested, ensuring quality improvement through systematic tracking.

Test Code - unittest

Testing Fundamentals

class DefectTracker:
    def __init__(self):
        self.defects = []

    def log_defect(self, defect):
        self.defects.append({'defect': defect, 'status': 'open', 'assigned_to': None})

    def assign_defect(self, index, developer):
        self.defects[index]['assigned_to'] = developer

    def fix_defect(self, index):
        if self.defects[index]['status'] == 'open':
            self.defects[index]['status'] = 'fixed'

    def retest_defect(self, index):
        if self.defects[index]['status'] == 'fixed':
            self.defects[index]['status'] = 'closed'

import unittest

class TestDefectTracking(unittest.TestCase):
    def test_defect_lifecycle(self):
        tracker = DefectTracker()
        tracker.log_defect('Login button not working')
        self.assertEqual(len(tracker.defects), 1)
        self.assertEqual(tracker.defects[0]['status'], 'open')

        tracker.assign_defect(0, 'Alice')
        self.assertEqual(tracker.defects[0]['assigned_to'], 'Alice')

        tracker.fix_defect(0)
        self.assertEqual(tracker.defects[0]['status'], 'fixed')

        tracker.retest_defect(0)
        self.assertEqual(tracker.defects[0]['status'], 'closed')

Execution Trace - 5 Steps

Step	Action	System State	Assertion	Result
1	Create DefectTracker instance	Empty defect list	defects list length is 0	PASS
2	Log a new defect 'Login button not working'	defects list has 1 defect with status 'open' and no assignee	defects list length is 1 and status is 'open'	PASS
3	Assign defect to developer 'Alice'	defect assigned to Alice	assigned_to is 'Alice'	PASS
4	Fix the defect	defect status changed to 'fixed'	status is 'fixed'	PASS
5	Retest the defect	defect status changed to 'closed'	status is 'closed'	PASS

Failure Scenario

Failing Condition: Defect status does not update correctly after fix or retest

Execution Trace Quiz - 3 Questions

What is the first status of a newly logged defect?

A closed

B fixed

C open

D assigned

Key Result

Tracking defects through clear statuses helps teams know what needs fixing and what is done, improving software quality by making the process visible and manageable.

Practice

1. Why is defect tracking important in software testing?

easy

A. It helps find and fix bugs faster

B. It increases the number of bugs

C. It slows down the development process

D. It hides problems from the team

Solution

1. Step 1: Understand the purpose of defect tracking

   Defect tracking is used to record and manage bugs found during testing.

2. Step 2: Identify the benefit of defect tracking

   By tracking defects, teams can fix bugs faster and improve software quality.

3. Final Answer:

   It helps find and fix bugs faster -> Option A

4. Quick Check:

   Defect tracking = faster bug fixing [OK]

Hint: Defect tracking speeds up bug fixing [OK]

Common Mistakes:

• Thinking defect tracking creates more bugs
• Believing it hides problems
• Assuming it slows development

2. Which of the following is the correct way to log a defect in a tracking system?

easy

A. Record the bug description, steps to reproduce, and severity

B. Only write the bug title without details

C. Ignore the bug if it is minor

D. Delete old bugs to keep the list short

Solution

1. Step 1: Identify key information for defect logging

   A good defect log includes description, reproduction steps, and severity to help fix it.

2. Step 2: Evaluate options for completeness

   Only Record the bug description, steps to reproduce, and severity includes all necessary details for effective defect tracking.

3. Final Answer:

   Record the bug description, steps to reproduce, and severity -> Option A

4. Quick Check:

   Complete defect info = correct logging [OK]

Hint: Log full bug details for clarity [OK]

Common Mistakes:

• Logging only the title without details
• Ignoring minor bugs completely
• Deleting bugs to reduce list size

3. Consider this defect tracking scenario:
Bug ID: 101
Status: Open
Severity: High
Assigned To: Dev Team
What is the likely outcome if the defect is tracked properly?

medium

A. The bug will be ignored and remain open

B. The bug will be deleted from the system

C. The bug will be fixed faster due to clear tracking

D. The bug severity will be lowered automatically

Solution

1. Step 1: Analyze the defect tracking details

   The bug has a clear status, severity, and assigned team, which helps prioritize fixing.

2. Step 2: Understand the effect of proper tracking

   Proper tracking ensures the bug is noticed and fixed faster by the responsible team.

3. Final Answer:

   The bug will be fixed faster due to clear tracking -> Option C

4. Quick Check:

   Clear tracking = faster fix [OK]

Hint: Clear status and assignment speed bug fixes [OK]

Common Mistakes:

• Assuming bugs get ignored if tracked
• Thinking severity changes automatically
• Believing bugs get deleted without fixing

4. A tester logs a defect but forgets to assign it to a developer. What is the main problem caused by this mistake?

medium

A. The defect will be fixed immediately

B. The defect will be deleted from the tracking system

C. The defect status will change to closed automatically

D. The defect may be ignored and not fixed on time

Solution

1. Step 1: Identify the role of assignment in defect tracking

   Assigning defects ensures someone is responsible for fixing them.

2. Step 2: Understand consequences of missing assignment

   Without assignment, defects may be overlooked and remain unfixed longer.

3. Final Answer:

   The defect may be ignored and not fixed on time -> Option D

4. Quick Check:

   Missing assignment = delayed fix [OK]

Hint: Always assign defects to avoid delays [OK]

Common Mistakes:

• Thinking defects fix themselves
• Believing status changes without action
• Assuming defects get deleted automatically

5. How does defect tracking improve overall software quality beyond just fixing bugs?

hard

A. By hiding defects from users to avoid complaints

B. By providing data to identify common problem areas and improve processes

C. By increasing the number of reported defects to delay release

D. By removing all testing steps to speed up development

Solution

1. Step 1: Understand the broader benefits of defect tracking

   Defect tracking collects data on bugs, helping teams find patterns and improve development.

2. Step 2: Identify how this data improves quality

   Using defect data, teams can fix root causes and improve processes, leading to better software.

3. Final Answer:

   By providing data to identify common problem areas and improve processes -> Option B

4. Quick Check:

   Defect data = process improvement = better quality [OK]

Hint: Use defect data to improve processes [OK]

Common Mistakes:

• Thinking defect tracking hides bugs
• Believing it delays release intentionally
• Assuming it removes testing steps