Let’s look into it. Suppose a tester finds a defect .The defect is assigned a status, new. The defect is assigned to development project manager who will analyze the defect. He will check whether it is a valid defect. If not , next the defect is checked whether it is in scope. Suppose you find a problem with the email functionality. But it is not part of the current release .Such defects are postponed Next, manager checks whether a similar defect was raised earlier . If yes defect is assigned a status duplicate If no the defect is assigned to developer who starts fixing the code. During this stage defect is assigned a statusin- progress. Once code is fixed. Defect is assigned a status fixed Next the tester will re-test the code. In case the test case passes the defect is closed. If the test cases fails again the defect is re-opened and assigned to the developer Consider a situation where during the 1st release of Flight Reservation a defect was found in Fax order which was fixed and assigned a status closed During the second upgrade release the same defect again re-surfaced. In such cases, a closed defect will be re-opened. That’s all to Bug Life Cycle
Download the sample Defect sheet
No comments:
Post a Comment