Defect Life Cycle

1.  New: When the Defect is reported for the first time, its status will be “NEW”. This means that is yet to be approved. The New defect can be a Assign, Rejected or Deferred. 2. Open/Assign: The lead of the tester study the New Defect . Then change status from New to Open/ Assign. And Assign to the respective developer. See you can make the two status separately that Open and Assign .Open : The defect is the Open but not still yet Assign. Assign: The defect Open and Assign to the Developer. 3. Resolved: Developer fixes the defect, assigned back to respective tester. By changing the status of the defect Resolved. The fixed defect need to be verify by Tester/Test Team . If the defect is correctly fixed then Tester change the status Verified else Reassign/Reopen. 4. Deferred: If the New or Assigned defect is decided to be fixed in next release instead of the current release then that defect status change to the Deferred. 5. Rejected: If the defect found to be invalid then it is rejected . The defect need to be rejected by either of Test team lead/Development lead . 6. Verified: If tester find there the defect is fixed then status change to Verified. 7. Closed: If tester feel that filed the defect is no longer exist in the software then it change the final status to be Closed. 8. Reopened/Reassigned: If the defect still exists even after the bug is fixed by the developer, the tester changes the status to Reopened/Reassigned.