Explain the defect template with its attributes. OR Explain Defect template.

201views

written 5.2 years ago by

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

i). Reporting a bug/defect properly is as important as finding a defect.

ii). If the defect found is not logged/reported correctly and clearly in bug tracking tools (like Bugzilla, Clear Quest etc.) then it won‘t be addressed properly by the developers, so it is very important to fill as much information as possible in the defect template so that it is very easy to understand the actual issue with the software.

Sample defect template

Abstract :

Platform :

Test case Name :

Release :

Build Level :

Client Machine IP/Hostname :

Client OS :

Server Machine IP/Hostname :

Server OS :

Defect Type :

Priority :

Severity :

Developer Contacted :

Test Contact Person :

Attachments :

Any Workaround :

Steps to Reproduce 1. 2. 3.

Expected Result:

Actual Result:

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