What is Defect Life Cycle?

The defect life cycle, also known as Bug Life cycle is the journey of a defect 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.

Defect Life Cycle — Workflow:

Defect Life Cycle States

· New — Potential defect that is raised and yet to be validated.

· Assigned — Assigned against a development team to address it but not yet resolved.

· 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.

· Closed — The final state of the defect that can be closed after the QA retesting or can be closed if the defect is duplicate or considered as NOT a defect.

· Reopened — When the defect is NOT fixed, QA reopens/reactivates the defect.

· Deferred — When a defect cannot be addressed in that particular cycle it is deferred to a future release.

· Rejected — A defect can be rejected for any of the 3 reasons; viz — duplicate defect, NOT a Defect, Non-Reproducible.

Difference between Defect, Bug, and Failure

1. Defect:

The bugs introduced by the programmer inside the code is called Defect.

Defect is defined as the deviation from the actual and expected result of application or software or in other words, defects are defined as any deviation or irregularity from the specifications mentioned in the product functional specification document. Defect is also solved by the developer in the development phase or stage.

Reasons for Defects:

· Any deviation from the customer requirements is called a defect.

· By giving wrong input may lead to defect.

· Any error in logic code may lead to defect.

2. Bug:
Sometimes most people are confused between defect and bug, they say that bug is the informal name of the defect. Actually, bugs are faults in the system or application which impact software functionality and performance. Usually, bugs are found in unit testing by testers.

There are different types of bugs, some of them are given below.

· Functional Errors

· Compilation Errors

· Missing commands

· Run time Errors

· Logical errors

· Inappropriate error handling

Above given these errors lead to bug.

3. Failure:

When a defect reaches the end customer, it is called a Failure.

Once the product is completed and it is delivered to the customers and if the customer finds any issues in the product or software then it is the condition of failure of the product.
In other words, if an end-user finds an issue in the product then that particular issue is called a failure.

Causes of Failure:

· Human errors or mistakes may lead to failure.

· Environmental conditions

· The way in which the system is used.

The flow of Bug to Defect:

Example:
Let’s see a defect by an example.

a=7

b=5

ans=a*b

print(“Addition of {} and {} = {}.”.format(a, b, ans))

When you compile and run this program you see the printed statement as below:

Addition of 7 and 5=35

This is a program of adding two numbers but the output is deviated from it’s the actual result which is 12. Now we have detected a failure. As the failure has been detected a defect can be raised.

Author:

Bharathi Balaji Rangaraj — Chennai, Tamil Nadu, India | Professional Profile | LinkedIn

Codeless Conf 2022: Register below

Codeless Conf 2022 | QA Talks Community

Blogger of the month program: Register below

Blogs | QA Talks Community

Website: https://www.tech-talks.info

Facebook: https://www.facebook.com/groups/1307221979364557

Twitter: @QTechtalks

Instagram: qatechtalks