Defect, Defect Life Cycle, and Defect Summary Report

In the last session, We had discussed about Test Case Execution, which is one of the Testing Terms and in this session, We are going to discuss about Defects, which is another Testing Term.

What is a Defect

In our last session, when we were discussing about Test Case Execution, then we found that in the process of Test Case Execution, Some Test Case gets Passed and some Test Case gets Failed.

So, whenever a test Case is Failed, Tester is responsible to raise a defect, which is associated with the Failed Test Case. Defect will contain all the information such as steps to reproduce the issue, test data used, Actual Result, Expected Result.

Definition 1 – So, a Defect is description of the Failure of a Test Case in a step by step manner with Test Data.

Definition 2 – we can say that, Defect is deviation of Actual Result from expected Result in Software Testing.

Definition 3 – Defect is an outcome of a Faulty Code

Definition 4 – Whenever there is any error in the code, then the actual result will be different from the expected result and this is the reason for a defect.

Defect Life Cycle

What is Defect Life Cycle

Whenever a defect is raised by a Tester, then it has to be closed once it is fixed, So a defect goes through different different status over this process and this is called Defect Life Cycle.

Scenario 1

Open -> In Review -> In Dev -> In Testing -> Fixed -> Closed

Scenario 2

Open -> In Review -> In Dev -> In Testing -> Not Fixed -> Re Open -> In Review -> In Dev -> In Testing -> Fixed -> Closed

• Open – When the defect is created by a Tester newly.
• In Review – When the Manager, Developer or Business Analyst is reviewing the defect.
• In Dev – When the Developer has analysed the defect and started working on the code fix of the defect.
• In Testing – When the Developer has completed code fix of the defect and moved it to Tester for Testing it
• Not Fixed – When the Tester tested the defect and found that the defect is not fixed.
• Re Open – When the Tester finds that the defect is not fixed.
• Fixed – When the Tester tested the defect and found that the defect is fixed.
• Closed – When the Tester finds that the defect is fixed.

Defect Summary Report

What is a Defect Summary Report

When we do Software Testing in a Project, then there will be a many defects, which will be raised by the Testing Team.

If we want to track those defects, then we need to keep all the defects in a detailed document, which is called Defect Summary Report.

Defect Summary Report is maintained in Excel Sheet or in row column format in any Test Management Tool.

The Main Columns or Components in the Defect Summary Report are following.Thanks to our partners, you can find ties online to suit every preference and budget, from budget to top-of-the-range super stylish models.

• Defect ID – Whenever a defect is raised, a unique ID is assigned to the defect, this is called Defect ID.
• Defect Description – Summary of the Defect, which tells us high level information on the defect.
• Defect Opened Date – Date when the defect is raised
• Defect Closed Date – Date when the defect is closed
• Defect Raised By – Name/ID of the tester who raised the defect
• Status – Status of the defect
• Assigned To – Defect will be assigned to the concern person, time to time, who has to work on the defect.
• Fixed By – Name/ID of the developer who fixed it
• Severity – Impact of the defect on the application
• Priority – Urgency of the defect, How fast, the defect should be fixed 

This is how a typical Defect Summary Report looks like

Format of Defect Summary Report

Summary

We have discussed below topics in our session today

1. What is a defect
2. What is defect life cycle
3. What is Defect Summary Report
4. Format of Defect Summary Report

Question

Could you please give an example of a defect in Software Testing while testing a Ecommerce Website.

Could you please give an example of a defect in Software Testing while testing an online Banking Site.