Bug Life Cycle

Let's understand Bug life cycle in simple terms,

"Bug life cycle talks about the complete life cycle of one bug from the time the bug is encounter, until the bug is closed".

1. As soon as, the test engineer encounter a bug, they will create a Bug report.
2. Intially the status of the bug is "New/ Open"
3. Then test engineer will send the bug report to the concern developer by changing the status as "Assigned".
4. The concern developer go through the bug report , reproduce the bug by following the steps in bug report and analyse were exactly the code changes are required and finally does the code changes.
5. Once code changes are done, concern developer changes the status as "Fixed".
6. Test engineer cannot blindly trust on developer. Hence, he do one round of "Re-Testing"  to ensure bug is fixed or not.
7. If the bug does not exists on the application, the test engineer changes the status as "Closed". Else, the test engineer changes the status as "Re-Opended".
8. Re-Opened  bugs are by default re-assigned to the same developer.
9. This process continues until the bug is closed.