← Back to Home

Defect Life Cycle

The Defect Life Cycle (also called Bug Life Cycle) describes the various states a defect passes through from identification to closure, defining how defects are tracked, managed, and resolved.

Defect life cycle answers: “What happens to a defect after it is reported?”

1. Definition

The Defect Life Cycle (also called Bug Life Cycle) describes the various states a defect passes through from identification to closure, defining how defects are tracked, managed, and resolved.

Defect life cycle answers: “What happens to a defect after it is reported?”

2. Purpose of Defect Life Cycle

  • Provide structured defect management
  • Track defect status clearly
  • Ensure accountability and transparency
  • Prevent defects from being missed or forgotten

3. Standard Defect Life Cycle States

3.1 New

  • Defect is logged by tester
  • Not yet reviewed

3.2 Assigned

  • Defect assigned to a developer or team

3.3 Open

  • Developer accepts the defect
  • Fixing activity starts

3.4 Fixed

  • Developer fixes the defect
  • Code changes completed

3.5 Re-Test

  • Tester re-tests the defect in a new build

3.6 Closed

  • Tester confirms fix works
  • Defect is officially closed

3.7 Reopened

  • Defect still exists after fix
  • Sent back to developer

4. Additional Defect States (Real Projects)

State Meaning
Rejected Not a valid defect
Duplicate Same defect already logged
Deferred Fix postponed to future release
Not Reproducible Cannot be reproduced
Won’t Fix Decision taken not to fix

5. Defect Life Cycle Flow (Conceptual)

New → Assigned → Open → Fixed → Re-Test → Closed
                         ↓
                       Reopened

6. Manual Tester’s Responsibilities

  • Log defects with accurate details
  • Assign correct severity and priority
  • Re-test fixed defects
  • Close or reopen defects appropriately
  • Communicate defect status clearly

7. Defect Life Cycle vs Test Case Life Cycle

Aspect Defect Life Cycle Test Case Life Cycle
Focus Issue resolution Validation
Ends with Closure Pass/Fail

8. Real-Time Example

  • Tester logs login failure → New
  • Lead assigns to dev → Assigned
  • Dev fixes issue → Fixed
  • Tester re-tests → Closed

9. Common Mistakes

  • Closing without proper re-testing
  • Reopening without evidence
  • Incorrectly rejecting valid defects
  • Poor communication during transitions

10. Interview-Ready Answers

Short answer:

Defect life cycle describes the stages a defect goes through from identification to closure.

Detailed answer:

The defect life cycle defines the workflow and states a defect passes through, ensuring effective tracking, fixing, and verification.

11. Key Takeaway

A well-managed Defect Life Cycle ensures no defect is lost, ignored, or incorrectly resolved.