What is Bug Life Cycle in Software Testing?

What is Defect/Bug Life Cycle in Defect Tracking?

A defect in a Software testing process will undergo different status like New, Open, Assigned, Rejected, Fixed, Reopen, ReTest, Closed, Deferred etc. before being considered as Closed or Rejected or Deferred.

So there are 3 different situations possible here in any manual or automated testing in Defect Management.

  • New – Closed
  • New – Rejected
  • New – Deferred (Postponed)

The time taken for the defect to be closed or rejected or deferred is called as a BUG LIFE CYCLE.

Explanation for Status:

[ultimatetables 53 /]

Defect Tracking:

With the email application example, we will explain the Defect/bug life cycle about how a new defect is created and tracked.

Once the email application development is completed, the tester tests the login page. While testing the login page, the tester founds out that the username field allows duplicate names. So the tester logs in to Test Management Software and registers a new defect.

Role of a Test Lead, Tester, Development Lead and Developer (DBA) in closing the defect:

[ultimatetables 54 /]

Other situations that arise during the handling of defects:

  • Tester reports to Testing Lead about a defect and Test Lead rejects it.
  • Test Lead is okay with the defect created by tester and reports the defect to the Development Lead and Development Lead rejects it.
  • Test Lead, Developer Lead is okay with defect and Developer works on the defect and reports to Testing Lead that the defect has been resolved. Again, Tester retests and reports that the defect has not been resolved and not closed. So, he reopens the defects once again.
  • Based on the priority or severity (The severity of the defect may be low, medium, high, critical and cosmetic etc. ) of the defect, the defect may not be closed at all or it may be deferred (postponed).

Defect/Bug Life Cycle Flow Chart:

Defect/Bug Life Cycle Flow Chart