Reporting a bug/defect properly is as important as finding a defect, if the defect found is not logged/reported correctly and clearly in bug tracking tools (like Bugzilla, ClearQuest etc.) then it wont 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 :
Testcase Name :
Release :
Build Level :
Client Machine IP/Hostname :
Client OS :
Server Machine IP/Hostname :
Server OS :
Defect Type :
Priority :
Sevierity :
Developer Contacted :
Test Contact Person :
Attachments :
Any Workaround :
Steps to Reproduce
1.
2.
3.
Expected Result:
Actual Result:
Defect Tracking Tools
Following are some of the commonly used defect tracking tools:
Bugzilla – Open Source Bug Tracking
Testlink – Open Source Bug Tracking
ClearQuest – Defect tracking tool by IBM Rational tools
HP Quality Center– Test Management tool by HP
