0
4.0kviews
Which parameters are considered while writing good defect report ? Also write contents of defect template.
1 Answer
0
167views
written 5.8 years ago by |
A defect report documents an anomaly discovered during testing. It includes all the information needed to reproduce the problem, including the author, release/build number, open/close dates, problem area, problem description, test environment, defect type, how it was detected, who detected it, priority, severity, status, etc.
After uncovering a defect (bug), testers generate a formal defect report. The purpose of a defect report is to state the problem as clearly as possible so that developers can replicate the defect easily and fix it.
DEFECT REPORT TEMPLATE: In most companies, a defect reporting tool is used and the elements of a report can vary. However, in general, a defect report can consist of the following elements.
ID | Unique identifier given to the defect. (Usually Automated) |
---|---|
Project | Project name. |
Product | Product name. |
Release Version | Release version of the product. (e.g. 1.2.3) |
Module | Specific module of the product where the defect was detected. |
Detected Build Version | Build version of the product where the defect was detected (e.g. 1.2.3.5) |
Summary | Summary of the defect. Keep this clear and concise |
Description | Detailed description of the defect. Describe as much as possible but without repeating anything or using complex words. Keep it simple but comprehensive. |
Steps to Replicate | Step by step description of the way to reproduce the defect. Number the steps. |
Actual Result | The actual result you received when you followed the steps. |
Expected Results | The expected results. |
Attachments | Attach any additional information like screenshots and logs. |
Remarks | Any additional comments on the defect. |
Defect Severity | Severity of the Defect. |
Defect Priority | Priority of the Defect. |
Reported By | The name of the person who reported the defect. |
Assigned To | The name of the person that is assigned to analyze/fix the defect. |
Status | The |
Fixed Build Version | Build version of the product where the defect was fixed (e.g. 1.2.3.9) |
ADD COMMENT
EDIT
Please log in to add an answer.