The defect lifecycle is the step-by-step procedure that a defect goes through. The lifecycle begins when a defect is caught, and it is closed when the defect is resolved.
A defect in software is a bug or an error that causes the software to behave in an unwanted or unexpected manner. It occurs when a developer makes a mistake while building that software.
The number of steps that a defect goes through depends on the organization and the software being developed. However, few common steps are explained below:
Defect Caught: When a new bug or error is identified and reported to be fixed.
Assigned: Once the bug is verified to be present, it is assigned to the development team. ** Open: The defect stays in this stage while the development team attempts to fix it. At this stage, one can also decide to either reject the bug or defer it to be resolved later on.
Rejected: The team lead can decide to reject the bug. The reason could be one of the following: a duplicate bug reported, not a bug, etc.
Deferred: The team lead can decide to defer the defect to be resolved later.
Fixed: Once the development team fixes the bug, it is moved to this stage for retesting.
Test: The tester or the quality assurance team tests the software again to assess if the defect was removed perfectly.
Reopen: If the defect is found again, it is reopened again and goes to the Open stage.
Verify: The tester or the quality assurance team re-tests the code for the same defect for further verification.
Closed: If the defect is not found again, it is closed.
Free Resources