Defect life cycle, also known as bug life cycle, is the journey of a defect or bug through different states in its entire life. The purpose of the defect life cycle is to easily coordinate and communicate the current status of a defect, which changes to various assignees, and make the defect fixing process systematic and efficient. The number of states that a defect goes through varies from project to project, but the following are the most common states in the defect life cycle:

• New: When a new defect is logged and posted for the first time, it is assigned a status as NEW.
• Assigned: Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to the developer team.
• Open: The developer starts analyzing and works on the defect fix.
• Fixed: The developer fixes the defect and assigns it back to the tester for retesting.
• Pending Retest: The tester tests the defect fix and assigns it back to the developer if the defect is still present.
• Retest: The developer fixes the defect again and assigns it back to the tester for retesting.
• Verified: The tester tests the defect fix and assigns it back to the ...