Any abnormality in software is known as Bug Or if application does not match with the requirements, it is reported as Bug. The elimination of bugs from the application depends upon the efficiency of testing done on it.
The different stages of a bug are as follows:
1. New
2. Open
3. Assign
4. Test
5. Verified
6. Deferred
7. Reopened
8. Duplicate
9. Rejected and
10. Closed
Description of Stages:
1. New: When the bug is logged for the first time, its stage is known as “NEW”. This means that the bug is not yet approved/validated.
2. Open: After a tester has logged a bug, the lead of the tester approves that the bug is valid and he changes the state as “OPEN”. (Depends upon Company's way of working, Tester can also change the status to "Open").
3. Assign: Once the Test lead validates the bug as “OPEN”, he assigns the bug to corresponding developer or developer team. At this stage bug status is changed to “ASSIGN”.
4. Test: Once the developer fixes and corrects the bug, he has to assign the bug to the testing team for next round of testing. Before he releases the software with bug fixed, he changes the state of bug to “TEST”. It ensures that the bug has been fixed and is again released for testing to the testing team.
5. Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this status have many factors. Some of them are priority of the bug may be low, lack of time for the release, bug cannot be fixed due to architecture reasons or the bug may not have major effect on the software.
6. Rejected: If the developer replicates the bug, and results are not same, he can reject the bug. And the status is changed to “REJECTED”.
7. Duplicate: If the bug is repeated twice or the two bugs mention the same concept/scenario of replication, then one of the bug statuses is changed to “DUPLICATE”.
8. Verified: Once the bug is fixed and the status is changed to “TEST”, the tester tests the bug. If the bug is not present in the software and is fixed properly keeping in mind other functionality is unharmed due to fixation of defect, he approves that the bug is fixed and changes the status to “VERIFIED”.
9. Reopened: If the bug still exists even after the bug is fixed by the developer or after fixing the defect it is creating problems in other part of application, the tester changes the status to “REOPENED”. The bug again follows the same life cycle once again.
10. Closed: Once the bug is fixed, it is tested by the tester. Tester validates that the bug no longer exists in the software, and changes the status of the bug to “CLOSED”. At this stage, bug is fixed, tested and approved.
The different stages of a bug are as follows:
1. New
2. Open
3. Assign
4. Test
5. Verified
6. Deferred
7. Reopened
8. Duplicate
9. Rejected and
10. Closed
Description of Stages:
1. New: When the bug is logged for the first time, its stage is known as “NEW”. This means that the bug is not yet approved/validated.
2. Open: After a tester has logged a bug, the lead of the tester approves that the bug is valid and he changes the state as “OPEN”. (Depends upon Company's way of working, Tester can also change the status to "Open").
3. Assign: Once the Test lead validates the bug as “OPEN”, he assigns the bug to corresponding developer or developer team. At this stage bug status is changed to “ASSIGN”.
4. Test: Once the developer fixes and corrects the bug, he has to assign the bug to the testing team for next round of testing. Before he releases the software with bug fixed, he changes the state of bug to “TEST”. It ensures that the bug has been fixed and is again released for testing to the testing team.
5. Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this status have many factors. Some of them are priority of the bug may be low, lack of time for the release, bug cannot be fixed due to architecture reasons or the bug may not have major effect on the software.
6. Rejected: If the developer replicates the bug, and results are not same, he can reject the bug. And the status is changed to “REJECTED”.
7. Duplicate: If the bug is repeated twice or the two bugs mention the same concept/scenario of replication, then one of the bug statuses is changed to “DUPLICATE”.
8. Verified: Once the bug is fixed and the status is changed to “TEST”, the tester tests the bug. If the bug is not present in the software and is fixed properly keeping in mind other functionality is unharmed due to fixation of defect, he approves that the bug is fixed and changes the status to “VERIFIED”.
9. Reopened: If the bug still exists even after the bug is fixed by the developer or after fixing the defect it is creating problems in other part of application, the tester changes the status to “REOPENED”. The bug again follows the same life cycle once again.
10. Closed: Once the bug is fixed, it is tested by the tester. Tester validates that the bug no longer exists in the software, and changes the status of the bug to “CLOSED”. At this stage, bug is fixed, tested and approved.
No comments:
Post a Comment