Defect Life Cycle in
Software Testing.
Defect or bug life
cycle is a cycle through which a defect goes in its lifetime. Defect life cycle
starts when defect is found and it ends when the defect is closed.
The life cycle of
defect can be shown below using flow diagram:
 |
| Defect Life Cycle |
Defect life cycle contains
following status of defect:
New: When the defect
is reported and posted for the first time. Then it is given New state.
Assigned: Once
reported the lead of the testing team will approved the defect is genuine and
the defect is assigned to corresponding developer. Then the status is changed
to Assigned.
Open: Once the defect
is assigned to developer the status of defect is changed to Open state.
Fixed: The status of
defect changed to Fixe when developer make the necessary change in code and
verified the changes.
Retest: After the
defect is fixed by developer it is assigned to Testing team for retesting. The
status is changed to Retest.
Reopen: Once the
testing team retests the fixed defect. It the defect is still present there
then the status of defect is changed to Reopened.
Close: If the testing
team retests the fixed defect and found out that the defect is fixed then the
status of defect is changed to Closed.
Duplicate: If the bug was reported earlier and again it is reported then the status is marked as Duplicate.
Rejected: If the bug
reported the testing team is considered as working fine then the defect is
rejected by the development team.
Deferred: The defect
reported by testing team is not of high priority and can be fixed in next
releases then the defect is marked as Deferred and will be fixed in upcoming
releases.
