Following are the points QA needs to know about bug life cycle in depth…

1️⃣ When QA finds the bug and logs it into the bug tracking system, the status will be ‘New’.

2️⃣ The developer will check if the raised bug is valid or not. If the bug is valid, the bug status will be ‘Assigned’; otherwise, ‘Invalid’.

3️⃣ When the developer starts analysing the bug, they mark the status as ‘Open’.

4️⃣ The developer may find that this bug is reported twice; in this case, the status will be ‘Duplicate’.

5️⃣ Developers may find that bug is not reproducible; in this case, the status will be ‘Rejected’.

6️⃣ If the bug priority is low and the Product Owner is fine with it, then we can take this bug in the subsequent release, and the status will be ‘Deferred’.

7️⃣ When the developer applies fixes for the bug, then the status will be ‘Fixed/Resolved’.

8️⃣ The next step is for QA to validate the fix, mark the status as Verified, and Close the bug.

9️⃣ If QA finds that the bug fix is not working, they reopen the bug and mark the status as ‘Re-opened’.

Omer Khan