Defect lifecycle in Testing Fundamentals - Full Explanation

Introduction

Imagine finding a problem in a product and wondering what happens to it next. The defect lifecycle explains the journey a problem goes through from discovery to resolution, helping teams track and fix issues efficiently.

Explanation

New

When a defect is first found, it is marked as New. This means it is logged and waiting to be reviewed by the team. No action has been taken yet to fix it.

New defects are freshly reported and need initial review.

Assigned

After review, the defect is assigned to a developer or team member responsible for fixing it. This step ensures someone is accountable for resolving the issue.

Assignment gives responsibility to fix the defect.

Open

The assigned developer starts working on the defect. The status changes to Open to show that the problem is actively being investigated or fixed.

Open means the defect is under active work.

Fixed

Once the developer believes the defect is resolved, they mark it as Fixed. This means the code or product has been changed to correct the problem.

Fixed indicates the defect has been addressed by the developer.

Retest

The testing team retests the product to confirm the fix works and the defect no longer appears. This step ensures the problem is truly solved.

Retest verifies the defect fix is effective.

Closed

If the retest is successful and no issues remain, the defect is Closed. This means the problem is fully resolved and no further action is needed.

Closed means the defect is completely resolved.

Reopen

If the defect still exists after retesting, it is Reopened. This sends it back to the developer for more work until it is fixed properly.

Reopen returns the defect for further fixing if the problem persists.

Deferred

Sometimes a defect is postponed to be fixed later due to low priority or resource limits. It is marked Deferred to show it is acknowledged but not fixed now.

Deferred defects are delayed for future fixing.

Rejected

If a reported defect is not valid or is a misunderstanding, it is Rejected. This means no fix is needed because it is not a real problem.

Rejected defects are invalid or not actual issues.

Real World Analogy

Think of a lost package in a delivery system. First, the package is reported missing (New). Then, a delivery person is assigned to find it (Assigned). They start searching (Open). When they find and fix the issue, like delivering the package (Fixed), the customer checks if it arrived (Retest). If the package is received, the case is closed (Closed). If not, the search starts again (Reopen). Sometimes, the search is delayed (Deferred), or the report was a mistake (Rejected).

New → Package reported missing

Assigned → Delivery person given the task to find the package

Open → Delivery person actively searching

Fixed → Package found and delivered

Retest → Customer checking if package arrived

Closed → Package received and case closed

Reopen → Package still missing, search restarts

Deferred → Search delayed due to low priority

Rejected → Report was a mistake, no package lost

Diagram

Diagram

┌─────┐    ┌─────────┐    ┌───────┐    ┌───────┐    ┌────────┐
│ New │ → │ Assigned│ → │ Open  │ → │ Fixed │ → │ Retest │
└─────┘    └─────────┘    └───────┘    └───────┘    └────────┘
                                         ↓            ↓
                                    ┌────────┐   ┌────────┐
                                    │ Reopen │   │ Closed │
                                    └────────┘   └────────┘

┌─────────┐
│ Deferred│
└─────────┘

┌─────────┐
│ Rejected│
└─────────┘

This diagram shows the flow of a defect through its lifecycle states and possible transitions.

Key Facts

Defect lifecycle → The process a defect follows from discovery to closure.

New → Initial state when a defect is reported.

Assigned → Defect is given to a developer to fix.

Fixed → Developer has corrected the defect.

Retest → Testing team verifies the fix.

Closed → Defect is resolved and no longer active.

Common Confusions

Thinking 'Fixed' means the defect is completely done.

Thinking 'Fixed' means the defect is completely done. 'Fixed' means the developer has made a change, but the fix must be verified by testing before closing.

Believing 'Closed' defects can never be reopened.

Believing 'Closed' defects can never be reopened. If a defect reappears after closing, it can be reopened for further work.

Assuming 'Rejected' defects are ignored.

Assuming 'Rejected' defects are ignored. Rejected defects are reviewed and found invalid, so no fix is needed.

Summary

The defect lifecycle tracks a problem from reporting to final resolution through clear stages.

Each stage has a specific role, like assigning responsibility, fixing, testing, and closing.

Understanding this flow helps teams manage defects efficiently and improve product quality.

Practice

1. Which state in the defect lifecycle indicates that a bug has been found but not yet assigned to a developer?

easy

A. New

B. Fixed

C. Retest

D. Closed

Solution

1. Step 1: Understand the meaning of 'New' state

   The 'New' state means the defect is just reported and has not been assigned yet.

2. Step 2: Compare with other states

   'Fixed' means the bug is corrected, 'Retest' means testing the fix, and 'Closed' means the bug is resolved and accepted.

3. Final Answer:

   New -> Option A

4. Quick Check:

   New = Bug found but unassigned [OK]

Hint: New means just found, not assigned yet [OK]

Common Mistakes:

• Confusing 'New' with 'Open' or 'Assigned'
• Thinking 'Fixed' means bug is new
• Mixing 'Retest' with initial bug discovery

2. Which of the following is the correct order of states in a typical defect lifecycle?

easy

A. New -> Assigned -> Open -> Fixed -> Retest -> Closed

B. Fixed -> New -> Assigned -> Open -> Retest -> Closed

C. New -> Open -> Assigned -> Fixed -> Closed -> Retest

D. Assigned -> New -> Open -> Fixed -> Retest -> Closed

Solution

1. Step 1: Recall the standard defect lifecycle sequence

   The typical order is New (reported), Assigned (developer assigned), Open (work started), Fixed (bug fixed), Retest (testing fix), Closed (bug resolved).

2. Step 2: Match the options with this sequence

   New -> Assigned -> Open -> Fixed -> Retest -> Closed matches the correct order exactly; others have states out of order.

3. Final Answer:

   New -> Assigned -> Open -> Fixed -> Retest -> Closed -> Option A

4. Quick Check:

   Lifecycle order = B [OK]

Hint: Follow the bug from report to closure in order [OK]

Common Mistakes:

• Mixing 'Assigned' and 'Open' order
• Placing 'Fixed' before 'Assigned'
• Confusing 'Retest' and 'Closed' positions

3. Consider this defect lifecycle snippet:

defect_states = ['New', 'Assigned', 'Open', 'Fixed', 'Retest', 'Closed']
current_state = 'Fixed'
next_state = defect_states[defect_states.index(current_state) + 1]
print(next_state)

What will be the output?

medium

A. Fixed

B. Retest

C. Open

D. Closed

Solution

1. Step 1: Find the index of 'Fixed' in the list

   'Fixed' is at index 3 in defect_states list.

2. Step 2: Calculate next_state using index + 1

   Index 3 + 1 = 4, so next_state = defect_states[4] which is 'Retest'.

3. Final Answer:

   Retest -> Option B

4. Quick Check:

   Next after Fixed = Retest [OK]

Hint: Index +1 gives next lifecycle state [OK]

Common Mistakes:

• Choosing 'Closed' instead of 'Retest'
• Confusing index positions
• Assuming current_state prints itself

4. A tester reports a defect and marks it as 'Closed' immediately without retesting. What is the likely issue in this defect lifecycle process?

medium

A. Opening defect after fixing

B. Assigning defect before it is New

C. Reopening defect without fixing

D. Skipping the Retest phase

Solution

1. Step 1: Understand the defect lifecycle phases

   After fixing, the defect should be retested before closing to confirm the fix.

2. Step 2: Identify the problem with skipping Retest

   Marking as 'Closed' without retesting skips verification, risking unresolved bugs.

3. Final Answer:

   Skipping the Retest phase -> Option D

4. Quick Check:

   Retest must happen before Close [OK]

Hint: Always retest before closing a defect [OK]

Common Mistakes:

• Closing defect without verification
• Confusing 'Closed' with 'Fixed'
• Ignoring defect assignment order

5. A defect is marked as 'Reopened' after failing retest. Which of the following best describes the next correct step in the defect lifecycle?

hard

A. Mark the defect as 'New' again and wait for retest

B. Close the defect immediately as it failed retest

C. Assign the defect back to the developer for fixing

D. Skip fixing and move to 'Retest' again

Solution

1. Step 1: Understand 'Reopened' state meaning

   'Reopened' means the defect was fixed but failed retesting, so it needs fixing again.

2. Step 2: Determine the next lifecycle step

   The defect should be assigned back to the developer to fix the issue properly before retesting.

3. Final Answer:

   Assign the defect back to the developer for fixing -> Option C

4. Quick Check:

   Reopened = Assign to developer [OK]

Hint: Reopened defects go back to developer for fix [OK]

Common Mistakes:

• Closing defect after failed retest
• Resetting defect to 'New' incorrectly
• Skipping fix and retesting again