 |
| Image ©2025 ux-qa.com |
Defect Lifecycle Management
These states ensure transparency, traceability, and consistency in managing defects throughout the testing process. This structured approach helps maintain software quality and reliability by ensuring bugs are adequately tracked and resolved.Defect lifecycle management within software testing, including Manual QA, describes the current state of a reported defect as it progresses from identification to resolution.
Terms
New
The defect or bug has been identified and reported for the first time.It is documented in the bug tracking system but has not been reviewed or confirmed.
Example: A tester finds an error message when clicking a button. The issue is reported with details and screenshots, and the status is marked as New.
Open
The defect has been reviewed and acknowledged by the development or QA team.The issue is confirmed as valid and needs to be addressed.
Example: After initial triaging, the development team agrees the bug is legitimate and sets the status to Open for fixing.
Fixed
The developer has made code changes to resolve the defect.The issue is considered resolved, but it hasn’t been verified by QA yet.
Example: A developer corrects the code causing the error. Once complete, they mark the bug as Fixed and notify QA for verification.
If the issue no longer occurs, it moves to the next stage.
Example: QA re-runs the test cases and confirms the error is resolved. The defect status is temporarily marked as Retested during this process.
Retested
The QA team verifies the fix by re-executing the failed test cases.If the issue no longer occurs, it moves to the next stage.
Example: QA re-runs the test cases and confirms the error is resolved. The defect status is temporarily marked as Retested during this process.
Closed
The defect is confirmed as resolved after successful retesting.The bug no longer occurs, and the issue is officially marked complete.
Example: After successful retesting, QA marks the defect as Closed to indicate it’s resolved.
Example: After successful retesting, QA marks the defect as Closed to indicate it’s resolved.
Reopened
If the bug reappears during retesting or later stages, it’s marked as Reopened.The issue returns to an Open state for further investigation.
Example: QA finds the issue persists despite the fix or encounters it again in a later build. The defect is Reopened for further examination.
These states ensure transparency, traceability, and consistency in managing defects throughout the testing process. This structured approach helps maintain software quality and reliability by ensuring bugs are adequately tracked and resolved.