When you find a bug and when you want to report it to the developers or to the concerned people, make sure that the report you are sending is clear and are in understandable format. The bug report should help the developers to understand the history of the issues. Here is the checklist created for reporting the bugs.
1. Mention the environment (operating system).
2. Mention the browser you used along with the version
3.Mention the name of the reporter.
4.Mention the date
5. Summary: Summarize the bug. The summary should be short and meaning full. The summary should be able to explain the nature of the bug. Don’t exceed the summary like a paragraph.
6. Description: Here you can describe the issues. But make sure it should not be like an essay.Otherwise it would be like a story. Where the developer might get board to read or may not have time to go through entire description. Explain the risk in the description part.
7. Mention the severity.
8. Steps to reproduce: This is the best way to explain where the issue has occurred. This will help the developers to get into the specific place and help them to solve it.
9. Snapshot: Attachment is also a good way of representing the bug. This is also a proof saying that the issue has occurred. Because some bugs are non-reproducible. So, in such case this would stand as a proof for those issues occurence. Good to send in .png format.
10. Give a meaning full name for the attachment
11. Check for the grammar mistakes and spelling mistakes.
12. Write the report in normal English word. Don’t use any complex words. So that developers may not Google it in search of getting meaning for those words.
13. Go through your report before you send it to the concerned people(if possible).
There are no standard template for the bug reporting. The reporting style varies from tester to tester.
“Writing a good bug report is a skill and it happens by practice"
- Pradeep Lingan
No comments:
Post a Comment