Skip to main content

Bug Life Cycle

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.


Bug Life Cycle, Software Testing Help, Manual Testing, Testing, QA, QC
Image Source Google

Labels:
Location: Jaipur, Rajasthan, India

Comments

Post a Comment

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.
Post a Comment
Read more

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.
Post a Comment
Read more

Structural Testing

Structural Testing is the type of testing in which user should have the knowledge of the code because in this testing user need to check the structure of the system. Structural Testing is White Box Testing.
Post a Comment
Read more