The Defect Life Cycle Explained


What is the defect life cycle?

Defect life cycle is a cycle which a defect goes through during its lifetime. It starts when defect is found and ends when a defect is closed, after ensuring it’s not reproduced. Defect life cycle is related to the bug found during testing.

How many phases the life cycle of defects have?

Defect Life Cycle States:

Active – The Defect is being addressed by the developer and investigation is 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 been verified by QA.

What is the defect life cycle in Jira?

The Jira bug life cycle consists of a definite number of steps such as New, Assigned, Opened, Duplicate, Differed, Not a Bug, Rejected, Reopened, Fixed, Retest, Verified, and Closed.

What is defect in STLC?

Defect Life Cycle, also known as Bug Life Cycle, is the journey of a defect, the cycle which a defect goes through during its lifetime. It varies from organization to organization and also from project to project, as it is governed by the software testing process and also depends upon the tools used

What is difference between bug and defect?

A bug is a deviation from the customer’s requirement. The functionality of an application not working as per the customer’s requirement is known as a defect

What is a defect in testing?

What is a defect in testing? A defect is a system error that doesn’t allow the intended action to be completed. Finding defects is the tester’s most important task. It’s important to start testing as early as possible because defects can be found throughout the entire software development process.

What is defect in manual testing?

Defect In Manual Testing

A defect is an anomaly which causes a deviation between the expected and actual results. It could be an error discovered once the application got deployed into production. Some software could show potential issues with both the internal and external features.

What causes most of the defects in SDLC?

Miscommunication of the requirements is one the most common problem in the software development process which causes an introduction of defects in the code. It means erroneous & lack of communication in the software development process

Who will close the defect?

“It’s a documentation issue.” The owner should still be the one closing the bug so that they have the chance to ensure that the revised documentation correctly addresses the issue.

Bug Life Cycle / What is Defect Life Cycle ?

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



Enjoy this blog? Please spread the word :)