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.


Enjoy this blog? Please spread the word :)