A Bug life cycle is the movement of a bug or defect in different stages of its lifetime, right from the beginning when it is first identified till the time is marked as verified and closed.
Depending on the defect management tool used and the organisation, we can have different states as well different nomenclature for the states in the defect life cycle.
Depending on the defect management tool used and the organisation, we can have different states as well different nomenclature for the states in the defect life cycle.
- New - A bug or defect when detected is in New state
- Assigned - The newly detected bug when assigned to the corresponding developer is in Assigned state
- Open - When the developer works on the bug, the bug lies in Open state
- Rejected/Not a bug - A bug lies in rejected state in case the developer feels the bug is not genuine
- Deferred - The Bug to be fixed in next release are marked as Deferred.
- Fixed/InTest - When a bug is resolved by the developer it is marked as fixed and assigned to the tester
- Reopened - If the tester is not satisfied with issue resolution the bug is moved to Reopened state
- Verified - After the Test phase if the tester feels bug is resolved, it is marked as verified
- Closed - After the bug is verified, it is moved to Closed status.
What is "bug leakage?" and What is "bug release?"
A defect which exists during testing yet unfound by the tester which is eventually found by the end-user is also called bug leakage.
A bug release is when a particular version of s/w is released with a set of known bug(s)/defect(s). These bugs are usually low severity and/or low priority bugs.
