Introduction
Defect Life Cycle is an important concept in software testing. It describes the journey of a defect from identification to closure.
What is Defect Life Cycle?
Defect Life Cycle (also called Bug Life Cycle) is the process through which a defect passes from discovery to resolution and closure.
It ensures proper tracking and management of defects in a project.
Defect Life Cycle Stages
- New: Tester logs the defect.
- Assigned: Defect assigned to developer.
- Open: Developer starts working on defect.
- Fixed: Developer fixes the defect.
- Retest: Tester verifies the fix.
- Closed: Defect successfully verified and closed.
- Reopened: If defect still exists after retesting.
- Rejected: Developer rejects defect (not valid).
- Deferred: Fix postponed to future release.
Defect Workflow Example
- Tester finds login issue → Status: New
- QA Lead assigns defect → Status: Assigned
- Developer fixes issue → Status: Fixed
- Tester retests → Status: Closed
- If issue persists → Status: Reopened
Common Defect Status in Tools
- New
- Open
- In Progress
- Fixed
- Retest
- Closed
- Rejected
- Duplicate
- Deferred
Real-World Example
Scenario: Payment gateway error
- Bug logged as "Payment failed for valid card"
- Assigned to backend developer
- Developer fixes API issue
- QA retests payment flow
- Bug marked as Closed
Defect Life Cycle Interview Questions
What is defect life cycle?
Defect life cycle is the journey of a defect from identification to closure.
What happens if defect is not fixed properly?
It is reopened and reassigned.
Who closes a defect?
QA tester closes the defect after successful retesting.
Frequently Asked Questions
What is difference between defect and bug?
Both are commonly used interchangeably to describe an issue in software.
Can a defect be deferred?
Yes, low-priority defects may be deferred to future releases.