When the bug is posted for the first time, its state is “NEW”. This means that a bug is not yet approved.
After a tester has posted the bug, the lead of the tester approves that the bug is genuine, and he changes the state as “Open”.
Once the lead changes the state as “Open”, he assigns the bug to the corresponding developer or developer’s team. The stage of bug is now “Assigned”
4. In Progress
Once the developer starts working on the bug, he changes the state of a bug as “in progress”.
5. Fixed/ Resolved
After fixing the issue by developers, the status of the bug or defect is changed to “Resolved’ and reassigned to a tester for retesting.
6. Retest/ Verified
The testing team again retests the fixed issue and its status is marked as retest until testing is complete.
If the bug still exists even after the bug is fixed by the developer, the tester changes the status as “Reopened”. The bug traverses the life cycle once again.
Once the bug is fixed, it is tested by a tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to “closed”. This state means that the bug is fixed, tested and approved.