The defect life cycle in software testing outlines the stages a defect goes through from identification to resolution. Key stages include 'new', 'assigned', 'open', 'fixed', 'awaiting retest', 'retest', 'verified', 'reopen', 'closed', and 'rejected', each representing a different status in the defect's journey. This process ensures that defects are systematically addressed and verified before closure.

1. What is a Defect Life Cycle or a Bug
Lifecycle in Software Testing
Defect life cycle is a cycle which a defect goes
through during its lifetime.

2. Defect Life Cycle Diagram

3. States of Bug Life Cycle
1 .New:
When a defect is signed and published initially.
It’s condition is given as new.
2 .Assigned:
After the specialist has published the bug, the
cause of the specialist grants that the bug is
authentic

4. States of Bug Life Cycle
3. Open:
At this condition the designer has began
examining as well as on the defect fix.
4. Fixed:
When designer creates necessary rule changes
and confirms the changes then he/she can create
bug position as ‘Fixed’ and the bug qualifies to
examining group.

5. States of Bug Life Cycle
5. Awaiting retest:
After solving the defect the designer has given
that particular rule for retesting to the specialist
6. Retest:
At this point the specialist do the retesting of the
modified rule which designer has given to him to
confirm whether the defect got set or not.

6. States of Bug Life Cycle
7. Verified:
The specialist assessments the bug again after it
got set by the designer.
8. Reopen:
If the bug still prevails even after the bug is set by
the designer, the specialist changes the position to
“reopened”.

7. States of Bug Life Cycle
9. Closed:
Once the bug is set, it is examined by the
specialist.
10. Rejected:
If the designer seems that the bug is not
authentic, he denies the bug.

8. Thank You