What is a defect?
A defect or a bug is an error in a program that causes the application to perform in an unintended manner, deviating from its requirements. Based on the urgency of fixing the defect, we can classify them on a scale of P0 to P3, with P0 defect having the most urgency to fix. Also, the defects can be classified based on their criticality or the impact to the functionality. Depending on the organisation, we can have different levels of defect severity ranging from minor to critical or show stopper.
To report a bug we have different Defect Management Tools like - Jira, Mantis, Bugzilla etc. Next, we will see the different components of a Defect Report.
Defect Reporting Template
- DefectId - A unique identifier of the defect.
- Summary - A one line summary of the defect, more like a defect title.
- Description - A detailed description of the defect.
- Build Version - Version of the build or release in which defect is found.
- Steps to reproduce - The steps to reproduce the defect.
- Expected Behavior - The expected behavior from which the application is deviating because of the defect.
- Actual Behavior - The current erroneous state of the application w.r.t. the defect.
- Priority - Based on the urgency of the defect, this field can be set on a scale of P0 to P3.
- Severity - Based on the criticality of the defect, this field can be set to minor, medium, major or show stopper.
- Reported By - Name of the QA, reporting the defect.
- Reported On - The date on which the defect was raised.
- Assigned To - The person to whom the defect is assigned in its current state. It can be the developer fixing the defect, the QA for verification of the fixed defect or the manager approving the defect.
- Current Status - The current status of defect (one of the states of the defect life cycle).
- Environment - The environment on which the defect is found - release, staging, production etc.