A defect life cycle outlines the journey a defect takes from being reported to being resolved. It varies by organization and project. Common states include: New - A potential defect is reported but not yet validated. Assigned - The defect is assigned to a development team to address but not yet resolved. Closed - The final state where the defect is closed after being retested and verified as fixed. Reopened - If the defect is not actually fixed, the QA team can reopen the defect.

1. http://www.tutorialspoint.com/software_testing _dictionary/defect_life_cycle.htm
Copyright © tutorialspoint.com
SOFTWARE TESTING - DEFECT LIFE CYCLE
What is Defect Life Cycle?
Defect life cycle, also knownas Bug Life cycle is the journey of a defect cycle, whicha
defect goes throughduring its lifetime. It varies fromorganizationto organizationand
also fromproject to project as it is governed by the software testing process and also
depends uponthe tools used.
Defect Life Cycle - Workflow:
Defect Life Cycle States:
New - Potentialdefect that is raised and yet to be validated.
Assigned - Assigned against a development teamto address it but not yet
resolved.
Active - The Defect is being addressed by the developer and investigationis

2. under progress. At this stage there are two possible outcomes; viz - Deferred or
Rejected.
Test - The Defect is fixed and ready for testing.
Verified - The Defect that is retested and the test has beenverified by QA.
Closed - The finalstate of the defect that canbe closed after the QA retesting or
canbe closed if the defect is duplicate or considered as NOT a defect.
Reopened - Whenthe defect is NOT fixed, QA reopens/reactivates the defect.
Deferred - Whena defect cannot be addressed inthat particular cycle it is
deferred to future release.
Rejected - A defect canbe rejected for any of the 3 reasons; viz - duplicate
defect, NOT a Defect, NonReproducible.