The bug or defect life cycle refers to the process that a software bug goes through from identification to resolution.
Here’s an overview of the typical stages:
New:
During test case execution, if the actual result does not match the expected result (according to the functionality), QA raises it as an issue. The reported defect is marked with a status of NEW.
Review:
After QA raises the issue, the Project Manager or QA Lead reviews the reported issues to confirm whether the reported item is indeed an issue. If it is confirmed as a valid issue, it will be assigned to the developers. If it is determined not to be an issue, it will be marked as NOT A BUG and closed.
Assigned:
The bug is assigned to the respective module lead or owner to address the issue.
Work-In-Progress:
Once the developer starts fixing the bug, the status of the bug changes to WORK IN PROGRESS.
Resolved:
After the developer makes the necessary code changes to resolve the defect, the status is changed to RESOLVED.
Verified/Closed:
The fix is ready and awaits testing to confirm that the defect has been successfully resolved. Once testing confirms the defect is fixed, it is marked as CLOSED in the tracking system.
Reopened:
If the defect still exists or recurs after being marked as fixed, it can be reopened for further investigation and resolution.