The most important activity in the STLC(Software Test Life Cycle) is raising bugs and bug status management.The typical states of a bug can be summarized as follows: 1. New 2. Open 3. Assign 4. Test 5. Verified 6. Deferred 7. Reopened 8. Duplicate 9. Rejected and 10. Closed Every project or product has predefined bug states that every bug goes through, depending on the bug management tool used or the project/customer requirement. However the typical Bug Life Cycle is illustrated below : Follwing are the definations for each state in the above illustration --
1. New: When the bug is posted for the first time, its state will be “NEW”. This means that the bug is not yet approved. 2. Open: After a tester has posted a bug, the lead of the tester approves that the bug is genuine and he changes the state as “OPEN”. 3. Assign: Once the lead changes the state as “OPEN”, he assigns the bug to corresponding developer or development team. The state of the bug now is changed to “ASSIGN”. 4. Test: Once the developer fixes 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 specifies that the bug has been fixed and is released to 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 state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software. 6. Rejected: If the developer feels that the bug is not genuine or is not reproducible after multiple attempts, he rejects the bug with tester's consent. Then the state of the bug is changed to “REJECTED”. 7. Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to “DUPLICATE”. 8. Verified: Once the bug is fixed and the status is changed to “TEST”, the tester retests the bug. If the bug is not present in the software, 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, the tester changes the status to “REOPENED”. The bug traverses the life cycle once again. 10. Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to “CLOSED”. This state means that the bug is fixed, tested and approved. It is very important for both development and testing team members to understand the bug life cycle very clearly and assign the right bug status to bugs after it is raised, fixed or verified. Seting wrong bug status can lead to chaos and will give a false picture of the product quality. This is because most of the quality reports or graphs use the bug state count matric as an important input. This article explains only the typical bug states, though in the actual practice the projects can have their own defined bug states which is supported by most of the bug tracking tools.
0 Comments
Leave a Reply. |
ContactCategories
All
Search TestingBasics.com![]() Custom Search |