what is bug life
The Bug Life Cycle refers to the different stages a defect goes through from its identification to its closure during software testing. It helps teams track and manage defects efficiently.
Thank you for reading this post, don't forget to subscribe!
Stages of Bug Life Cycle
- New
- When a defect is first identified, it is assigned the status “New.”
- Assigned
- The defect is assigned to a developer or relevant team member for analysis.
- Open
- The developer starts analyzing and fixing the defect.
- In Progress / Work in Progress (Optional)
- Some organizations use this stage to indicate that the defect is actively being worked on.
- Fixed
- The developer resolves the defect and marks it as “Fixed.”
- Pending Retest (Optional)
- The fix is deployed to a test environment and awaits validation by the testing team.
- Retest
- Testers re-execute the test case to verify if the bug is properly fixed.
- Verified
- If the bug no longer exists, it is marked as “Verified.”
- Closed
- If the fix is successful, the defect is marked “Closed.”
Other Possible Statuses
- Reopened: If the bug persists after testing, it is reopened and sent back to the developer.
- Deferred: If the defect is of low priority or cannot be fixed in the current release, it is deferred for future consideration.
- Duplicate: If a similar bug already exists, it is marked as a duplicate.
- Rejected: If the reported issue is invalid or not considered a bug, it is rejected.
Bug Life Cycle Flow Chart
scssCopyEditNew → Assigned → Open → Fixed → Retest → Verified → Closed
↘ Reopened (if issue persists)
Each organization may customize the Bug Life Cycle based on their workflow, tools, and project needs.
