Defect Life Cycle

Defect Life Cycle (Bug Life cycle/Error Life Cycle) is the journey of a defect from its identification to its closure. The Life Cycle varies from organization to organization and is governed by the software testing process the organization or project follows and/or the Defect tracking tool being used.

Description of Various Stages:

• New : Tester found new bug and report it to test lead.
• Open : Test lead open this bug and assign it to the developer.
• Assign : Developer has three choices after assigning the bug.
• Reject :He can say that this is not a bug because of some hardware or other problems you might getting defect in application..
• Differed : He can postpone bug fixing according to priority of bug.
• Duplicate : If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to “DUPLICATE”.
• Fixed : If there are no such conditions like reject, duplicate the developer has to fix the bug.
• Testing : Test the whole application to find the defects if the defect is still there they will re-open the bug and if bug is not there it will move to verify.
• Re-open : If defect raised during testing we re-open bug.
• Verify : Retest whole application.
• Close : Close the application.                                                               

• Status	Alternative Status
  NEW
  ASSIGNED	OPEN
  DEFERRED
  DROPPED	REJECTED
  COMPLETED	FIXED, RESOLVED, TEST
  REASSIGNED	REOPENED
  CLOSED	VERIFIED