“Hi bug! I’ve heard a lot about you” —Get to know all the details about bugs
By now you should know how to write a good bug title. Let’s say 80% of all the information can be found in the title. Now I am going to teach you how to add the 20% of extra information that makes the bug 100% complete.
Let’s write the details of this bug:
[iOS] [Graphical] [FAQ] The “We Are Testers” icon appears blurry
Steps to reproduce:
These are short, easy to understand steps that lead the reader towards the unexpected behavior. For example:
- Open the page www.we-are-testers.com
- Click on “FAQ” in the footer
- Scroll down to the “How to report bugs?” paragraph
- Observe the “We are testers” icon
Actual result:
After following the “Steps to reproduce”, the actual result is the unexpected behavior that appears.
The “We Are Testers” icon appears blurry
Expected result:
After having followed the “Steps to reproduce”, this should have happened instead of the “Actual result”.
The “We Are Testers” icon is correctly displayed
Attachments:
Attaching a screenshot or video helps the developer to visualize the bug.
Sometimes other additional attachments are asked by the client (Crash log, Event log, Monkey test log, etc.)
