|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Home | Computers & Technology | Software In the very first day of my career as a software tester I came across the term "Bug Life Cycle" . I started learning some related documents from web. There are more documents than one can be patient enough to read about "Bug Life Cycle" . Every author had a different view of looking into the matter. But basically everyone focused on the stages of "Bug Life Cycle" rather than people involved in it . In discussions , pictures the bug played a bigger role than anyone else. Then I started learning "Bug Life Cycle" from the view of everyone involved in it . And I found it easier to understand that way . My review "Role Players of Bug Life Cycle" represents my attempt in that direction . Possible Stages Of Bug : A bug goes through several stages before it reaches its final stage . Anyway a bug ends finally in any of the following stages . Closed Rejected Deferred Postponed Prior to that a bug goes through hands of different people and accordingly several stages like New , Assigned ,Open ,Fixed,Pending Retest,Retest,Reject,Pending Reject,Reopen etc . A Normal Life Cycle : Here are steps of a normal bug life cycle , where the bug is finally fixed . <1>A tester finds a bug in the application and informs the test lead . <2>The test lead checks if the bug is valid or not. <3>If the bug is valid then test lead reports it to development lead. Corresponding bug stage : “New” <4>The development lead assigns the bug to a developer . Corresponding bug stage : “Assigned” <5>The developer works on the bug . Corresponding bug stage : “Open” <6>The developer fixes the bug and reports to development lead . Corresponding bug stage : “Fixed” <7>The development lead reports to test lead about this . Corresponding bug stage : “Pending Retest” <8>Test lead passes it to the tester for retest. Corresponding bug stage : “Retest” <9>The tester retests the application with the changes done and satisfied . The tester closes the bug. Corresponding bug stage : “Closed” People and their roles : People who are involved in the “Bug life cycle” are tester,developer,test lead and development lead. A>The tester: The role of a tester is not limited to finding bugs in the application . A tester can give suggestions for the enhancement of the application. It is the tester , who first finds and reports the bug to the test lead as “New”. After all changes are made , the tester retests the application to see that the bug is fixed and changes made do not affect the application. If the tester finds that same problem persists, then after consulting with test lead he assigns “Reopen” state to the bug. Otherwise if the application works fine with the changes , he marks the bug as “Closed”. If a bug is rejected by the development team , the tester tries to reproduce the bug. If the bug is reproduced he assigns “reopen” state to the bug. B>The test lead: After confirming that the reported bug is valid ,the test lead reports it to the development lead. If the test lead feels that the reported bug can not be tested with currently available data or functionality, he changes the state of the bug to “postponed”. Which means testing is postponed to indefinite time period. If the test lead finds that the bug has no importances and testing can/should be postponed then he changes the state of the bug to “deferred”. After receiving “pending retest” from development lead , test lead assigns the bug to a tester for retest. After receiving “pending reject” from the development lead, the test lead after confirming with the tester changes state of the bug to “rejected”. C>The developer: After the bug is assigned to the developer , he tries to reproduce it following the steps mentioned by the tester. If reported bug is reproduced ,he starts working on it and changes its state to “Open” . If he feels that he has fixed the bug ,he marks the bug as “fixed” and passes it to the development lead. If the developer fails to reproduce the bug or feels that it is not a bug really, then he changes its state to “Reject” and sends it to development lead. D>The dev.lead: Upon receiving the bug from the test lead, the development lead assigns it to a developer and changes its state to “Assigned”. After receiving “Reject” from the developer, dev.lead marks the bug as “Pending Reject” and sends it to the test lead. After receiving “Fixed” from the developer , dev.lead marks the bug as “Pending Retest” and sends it to the test lead . If the dev. lead feels that the reported bug can not be tested with currently available data or functionality, he changes the state of the bug to “postponed”. Which means testing is postponed to indefinite time period. If the dev. lead finds that the bug has no importances and testing can/should be postponed then he changes the state of the bug to “deferred”. Conclusion : In this review I have not taken the scale of organization into account which may influence the life cycle of the bug. One of the important aspects of testing is the communication of bug between the tester and the developer.There are several ways of communication of bug between developer and tester. It depends on type,size and requirement of the project undertaken. Ready made tools for bug communication are also available in the market i.e. Bug Tracking Systems. Article Source: http://www.articlewheel.com
Prepared by: Smruti Ranjan Kar
|
  RSS Feeds by Category |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
