Bug Life Cycle

Before looking at Bug life cycle, we should know what is a bug.In terms of software,bug can be defined as the abnormal behavior of the software.

               In SDLC, the bug has a life cycle & it should go through the life cycle to be closed.

Bug Life Cycle

1 New - When a bug is introduced for the first time,its state is 'New'.
2 Open - After bug is posted by tester,the lead tester verifies if bug is genuine and changes its state to    'OPEN'.
3 Assign - Once bug's state is changed to 'Open',bug is assigned to corresponding to developer and the state is changed to 'Assigned'.
4 Resolve - After developer fixes bug, he has to assign the bug to testing team for the further testing(regression testing).At this point, bug's state is changed to 'Test or Resolve' which specifies that the bug has been fixed & is released to testing team.
         4.1 Deferred - When the bug is expected to be fixed in next release, its state is changed to 'Deferred'.
        4.2 Rejected - If the developer feels that bug is not genuine,he changes its state to 'Rejected'.
       4.3 Duplicate - If bug is repeated or two bugs mention the same concept of bug, then bug state is changed to 'Duplicate'.
5 Verified - After bug is fixed and tested and if bug no longer exists in the software , the state of bug is changed to 'Verified'.
6 Reopened - If the bug still exists even after the bug is fixed by the developer, the tester changes state to 'Reopened' & bug traverses the life cycle again.
7 Closed - Once bug is verified, bug's state is changed to 'Fixed'.