Bug Life Cycle

Bug Life Cycle (Defect Life cycle) is the journey of a defect from its identification to its closure. The Life Cycle varies from organization to organization and is governed by the software testing process the organization or project follows and/or the Defect tracking tool being used.

Nevertheless, the life cycle in general resembles the following:

1. NEW
   When the bug is posted for the first time its status is NEW.
2. ASSIGN:
   When the lead of testing team feels that the bug is genuine, he assigns the bug to the development team, hence the status is changed to ASSIGN.
3. OPEN:
   When the developer analyzes and works on the bug to fix it, the status is changed to Open.
4. FIXED:
   When the bug is fixed by the developer, the status is changed to Fixed.
5. PENDING RETEST:
   After fixing the bug the developer give the specific piece of code to the tester to test again, hence the bug is at the tester’s end so the status is changed to Pending Retest.
6. RETEST:
   The tester tests the bug again so the status is Retest.
7. VERIFIED:
   After testing again if the tester feels that the bug is now fixed, he/she changes the status to Verified.
8. REOPEN:
   If the tester feels that the bug is still not fixed, he/she change the status to reopen.
9. CLOSED:
   If the bug is fixed, the status is changed to Closed.
10. DUPLICATE:
    If the bug is repeated twice or the two bugs mention the same concept of bug, then one bug is changed to duplicate.
11. REJECTED:
    The status is changed to Rejected if the developer feels that the bug is not genuine.
12. DEFERRED:
    The status is changed to deferred if the developer feels it might be fixed in the later releases or the bug has low priority.
13. NO BUG:
    The status is changed to No Bug if there is no change in functionality of the application.