i) Defect ID: - Any unique name called identification number
(Alpha Numeric).
ii) Defect Description: - Details about the defect
iii) Test case id: - The corresponding test case id for
tracking which case had been failed.
iv) Tester: - Name of the tester who found the defect.
v) Product version: - Version of the product.
vi) Build version:- every product version has many build versions
so we will here mention the name of build version on which defect was found.
vii) Priority:- importance of defect based on business
/customer.
viii) Severity:- Importance of defect based on functionality.
xi) Status:- status of defect(Open, Alpha & Beta verified,
Inquiry, Build hold, Re-assigned, Assigned, Close, In progress etc)
x) Reproduce able or
not:- Yes/No
If
reproduceable:
Step:
1)
Launch the application
2)
Enter the numeric value
3)
Enter valid password
4)
Click on default button
If
not reproduceable:
Attach screen
shots , database dumps
xi) Reporting to:- Corresponding developer who will fix it.
xii) Remarks:- Comment optional
Status: Status of defect
New: transfer provides new status while reporting (for the
first time)
Open: Developer / Dev lead / DTT opens the defect (DTT-defect tracking
team)
Reject: Developer /Dev lead / DTT rejects if the defect is
invalid or defect.
Fixed Developer provides fixed status after fixing the
defect
Deferred: Developer provides closed status after performing
confirmation testing
Closed: Tester provide closed status after performing
confirmation(re integration testing) testing.
Re-open: Tester re-opens the
defect with valid reason and proofs.
Hello,
ReplyDeleteThe Article on Manual Testing defect report template is nice give detail information about it.Thanks for Sharing the information about Manual testing
Software Testing Company
The Article on Mobile testing Services Map is awesome nice pie chart description, thanks for sharing the information about it.Mobile app testing Services and load testing services.
ReplyDelete