Statuses associated with a bug:
Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Bug Report @ OneStopTesting
Forum Discription: After Creating the Test Plan, Writing the Test Cases and using them, Finally We need to generate those Bug Reports which Proves that Testers are Good enough & most importantly Indispensable.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=705
Printed Date: 02Jul2024 at 2:22pm
Topic: Statuses associated with a bug:
Posted By: Rupali
Subject: Statuses associated with a bug:
Date Posted: 05Apr2007 at 4:06am
New:
When a bug is found/revealed for the first time, the software
tester communicates it to his/her team leader (Test Leader) in order to
confirm if that is a valid bug. After getting confirmation from the
Test Lead, the software tester logs the bug and the status of ‘New’ is
assigned to the bug.
Assigned:
After the bug is reported as ‘New’, it comes to the Development
Team. The development team verifies if the bug is valid. If the bug is
valid, development leader assigns it to a developer to fix it and a
status of ‘Assigned’ is assigned to it.
Open:
Once the developer starts working on the bug, he/she changes the
status of the bug to ‘Open’ to indicate that he/she is working on it to
find a solution.
Fixed:
Once the developer makes necessary changes in the code and verifies
the code, he/she marks the bug as ‘Fixed’ and passes it over to the
Development Lead in order to pass it to the Testing team.
Pending Retest:
After the bug is fixed, it is passed back to the testing team to
get retested and the status of ‘Pending Retest’ is assigned to it.
Retest:
The testing team leader changes the status of the bug, which is
previously marked with ‘Pending Retest’ to ‘Retest’ and assigns it to a
tester for retesting.
Closed:
After the bug is assigned a status of ‘Retest’, it is again tested.
If the problem is solved, the tester closes it and marks it with
‘Closed’ status.
Reopen:
If after retesting the software for the bug opened, if the system
behaves in the same way or same bug arises once again, then the tester
reopens the bug and again sends it back to the developer marking its
status as ‘Reopen’.
|
|