The quality of a bug report will be determined by its written documentation and attachments (screenshots and screencasts).
The bug submission form should look like this:
All informations should be entered as detailed but compact as possible.
The bug title should be – straight and precise!
It should contain: Element / Origin / Function – of the bug.
Wrong: No search results
Correct: Search results not displayed when entering a valid search on the homepage.
Read our blogpost “Writing the perfect bug title“
Steps to reproduce:
Bugs have to be reproducible and they need a detailed step by step guide how they can be reproduced.
The first step always contains the first site (and URL in case of a web product) you see on the current product. You do not need to number the steps, our system does that automatically.
- Go to www.theproductswebsite.com. Open the app.
- Locate the search function in upper right corner
- Enter any search subject, for example “San Francisco”.
- Click on search now or hit the enter button
The expected result of the steps you just described, are to be entered here.
As always details are the key
Wrong: Town name search function works
Correct: After entering the town name “San Francisco” I’ve expected, that the according results will be displayed. If there are no hotels in the town “San Francisco”, there should be displayed a message, e.g.:” There are no hotels available in your town”
What actually happens after you follow the steps to reproduce, as detailed as possible.
This is really important information, because it describes the actual bug.
Wrong: Town name search function don’t work
Correct: After you click on “Search now”, there is no action or expected behavior. There is no new browser page with search results and the user doesn’t get any message or notification about that. The button “Search now” is without any functionality.
There must be at least one Attachment attached to every bug reported.
You can read more about attachments here.