Bug life cycle is a cycle of a Bug from when it is generated to when it is closed. Following phases of Bug life Cycle
- New: When QA team find a new bug we provide 'New' status for that Bug.
- Open: When QA team add that Bug and Team lead approve the bug to genuine then status of that bug is 'OPEN'
- Assign: When any bug assign to the Developer then status change to 'Assign'.
- Rejected: When developer found that bug is not genuine and he/she unable to reproduce the bug then developer change the status to 'Rejected'.
- Deferred: When developer found that bugs is not related to current work and will be consider in later modules then developer change the status of bug to 'Deferred'.
- Test: Once the developer fix the bug and assign to the QA team then QA team need to retest the bug to verified that the issue has been fix on not. 'Test' status means bug has been fixed and assign beck to Testing team.
- Reopened: If QA team found that issue still not been fixed then QA team change the status to 'Reopened' and again assign to the developer team.
- Verified: If QA Team found that issue has been fix now and testing team verified the issue and ensure that issue will not be generated in future , QA team change the status to 'Verified'.
- Closed: After verified by QA team to ensure issue has been fix they change the status to 'Closed'. This status means bug has been tested , verified and approved.
Image Source Google |
Comments
Post a Comment