Bug Life Cycle and Description:
New: Default status of the bug should be as NEW.
Checked In: As soon as the developer understood and resolved the bug; he will changed the NEW status as CHECKED IN before releasing the build.
In Progress : Developer may change the status to IN PROGRESS if bug needs to be resolved in many days
New: Default status of the bug should be as NEW.
Checked In: As soon as the developer understood and resolved the bug; he will changed the NEW status as CHECKED IN before releasing the build.
In Progress : Developer may change the status to IN PROGRESS if bug needs to be resolved in many days
Fixed It Later / Deferred: Usually Low Priority bugs marked as FIXED IT LATER by the developer
Not a Bug: If lead/verifier/ developer consider the bug as Not a Bug then he may mark and change the status also providing healthy comments against it.
Re-Opened: If bug still exists or QA not satisfied with the solution in the new build then tester should open the bug again by selecting the status as RE-OPENED.
Closed: If bug is successfully resolved and verified by the tester then it status should be marked as CLOSED.
Suggestion: Tester should has the enough knowledge about the quality principles and if he found any lack in the requirement or testing phase than he can report the SUGGESTION to make the application more efficient
Not a Bug: If lead/verifier/ developer consider the bug as Not a Bug then he may mark and change the status also providing healthy comments against it.
Re-Opened: If bug still exists or QA not satisfied with the solution in the new build then tester should open the bug again by selecting the status as RE-OPENED.
Closed: If bug is successfully resolved and verified by the tester then it status should be marked as CLOSED.
Suggestion: Tester should has the enough knowledge about the quality principles and if he found any lack in the requirement or testing phase than he can report the SUGGESTION to make the application more efficient
0 comments :
Post a Comment