Defect/Bug Life Cycle

Defect/ Bug Life Cycle

Defect life cycle also known as bug life cycle. Defect life cycle/ Bug life cycle is the journey of bug from initiation to closure during its life time. It may different from organization to organization and may project to project.

Business Analyst/ Scrum Master will monitor till closure of the defect, it may different from organization to organization.

New : During testing of the application if tester find/observed any issue then tester will raise the issue(Bug/Defect)

Assigned : Once tested raised the defect it will be assigned to the development team to fix/resolve  the defect.

Open : Development team will open the defect.

Review : Development team will review the defect, whether it is genuine issue or not.

Rejected : If development team feels it is not a genuine defect then they can reject the ticket with mention their comments.

Deferred – When a defect cannot be addressed in this cycle then it is deferred to future release.

Duplicate: Development team will mark as a duplicate if it is duplicate defect means which is already raised previously.

Fixed : If development team identifies as it is genuine bug then team will fix the issue. In some organizations once, developer fixed the code development manager/team lead will review the code, whether it is impacting any other functionality or not. And they fixed the issue again they will assign to testing team for testing.

Retest : Testing team will test the defect which is assigned by development team.

Close : If testing team feels defect is resolved then they will close the defect ticket.

Reopen : If testing team feels still issue/defect not resolved then again they will reopen the ticket and assign back to development team to resolve the issue, again same cycle will follow.

I hope it helped you to understand  Defect Management Life Cycle 

Defect/Bug Life Cycle in Software Testing


Tweet 20