Bug lifecycle Stages

Bug lifecycle – states-I

New:    When the bug is posted for the first time, its state will be “NEW”. This means that the bug is not yet    approved.

Open:   After a tester has posted a bug, the lead of the tester approves that the bug is genuine and he changes   the state as “OPEN”.

Assign:  Once the lead changes the state as “OPEN”, he assigns the bug to corresponding developer or developer team. The state of the bug now is changed to “ASSIGN”.

Test:     Once the developer fixes the bug, he has to assign the bug to the testing team for next round of testing. Before he releases the software with bug fixed, he changes the state of bug to “TEST”. It specifies that the bug has been fixed and is released to testing team.

Deferred:The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software.