Ever goggled for “sample bug report”?? I did, N number of search results are shown pointing to an equivalent bug anatomy. I agree that bug report template depends upon your application’s domain and scope. And also any “VALID” bug is raised with an aim to be fixed. But as a tester what else you can cite, to create an exceptional bug report.
Customer Impact: It’s in turn an implication of bug “Severity”. But still we can list the following
- How the observed deviation or exception may disturb your customer.
- What are the customer bases that are likely to be affected by this defect?
Behavior of the feature in previous run: This field talks about the history. Guess this will be part of regression defects or in any upgrade project.
Time of occurrence: Testers ensure to enclose logs, stack trace, screenshot and video. Yet provide time of incidence. This aids dev team to quickly spot the issue.
Bench-marking with competitor products: Always analyze how component in hand behaves in par with competitor product. This improves tester’s business skills.
Suggested Fix: Most of the testers avoid this, remember every tester simulate a customer. Feel free to share your insight about the way you want the product to be sculptured.
The fields quoted above might be in your bug tracking tool as well, if so please waive them. I have cited the provisions that are part of “eXceptional Bug Report” from my end. Now it’s your turn.
No comments:
Post a Comment