Bug Life Cycle is also REFERRED to as Defect life cycle. It is a software testing cycle where a bug or defect goes through its lifetime.

It consists of several stages:

1. A tester finds a bug. He or she assigns it with either Open or New status.
2. The found bug is then assigned to a PARTICULAR development project coordinator. He or she analyzes the nature of the bug. The manager will determine WHETHER the bug is valid or not. If the defect is not valid, then the project coordinator will reject the bug with the status “Rejected.”
3. When it is not, the next step is to check whether the scope of the defect is checked. In the case the defect is not part of the current release, then that defect is postponed.
4. In this stage, the tester evaluates whether a defect similar to the current one had EARLIER been discovered. If yes, the bug is assigned with a “Duplicate” status.
5. The bug is now assigned to a DEVELOPER. It is assigned with a status “In Progress.”
6. After fixing the code, the bug is assigned with a status “Fixed.”
7. Last but not least, the tester re-tests the code. If the code passes to what we refer to as test case, the bug is “Closed.” If the test case fails, the defect is re-opened. Once again, it is assigned to the developer until it passes test case.

Bug Life Cycle is also referred to as Defect life cycle. It is a software testing cycle where a bug or defect goes through its lifetime.

It consists of several stages: