Answer:
✰ When a tester finds a bug .The bug is assigned with new or open status.
✰ The bug is assigned to development project manager who will analyze the bug .He will check whether it is a valid defect. If it is not valid bug is rejected, now status is rejected.
✰ If not, next the defect is checked whether it is in scope. When bug is not part of the current release such defects are postponed.
✰ Now, Tester checks whether similar defect was raised earlier. If yes defect is assigned a status duplicate.
✰ When bug is assigned to developer. During this stage bug is assigned a status in-progress.
✰ Once code is fixed. Defect is assigned with fixed status.
✰ Next the tester will re-test the code. In case the test case passes the defect is closed.
✰ If the test case fails again the bug is re-opened and assigned to the developer. That's all to Bug Life Cycle.
✰ The bug is assigned to development project manager who will analyze the bug .He will check whether it is a valid defect. If it is not valid bug is rejected, now status is rejected.
✰ If not, next the defect is checked whether it is in scope. When bug is not part of the current release such defects are postponed.
✰ Now, Tester checks whether similar defect was raised earlier. If yes defect is assigned a status duplicate.
✰ When bug is assigned to developer. During this stage bug is assigned a status in-progress.
✰ Once code is fixed. Defect is assigned with fixed status.
✰ Next the tester will re-test the code. In case the test case passes the defect is closed.
✰ If the test case fails again the bug is re-opened and assigned to the developer. That's all to Bug Life Cycle.
Previous Question | Next Question |
Define severity and priority of bug? | How to measures customer satisfaction for the Product? |