What makes a good Bug Report?

posted in: Software Testing | 0

Sometimes that means it is quicker to talk and sometimes, due to the complexity of the bug, it is easier to add all the information to the ticket currently in play and then discuss this as well.

So what makes a good bug report? 

From my experience, keeping the report minimal, factual & on point. A brief description of the actual bug using Given, When, Then, works really well, but not compulsory. The platform versions you tested it on, including project names and builds.

I always include at least one image as I find these speak clearer than words most of the time and I also find an image also helps to facilitate the written word too. I use Greenshot to capture onscreen images and it has a built in editor too which is really easy to use.

For more interactive bugs, I include a short video. I use SRecorder which is very simple to use and provides good quality playback. (Just be aware not to install all the rubbish they try to force upon you when installing. I nearly fell for it! It is free, so we cannot complain.)

With these three mediums, I have very little comeback when the developer/designer reworks the code to fix the bugs, thus increasing efficiency and turnaround.

For a tester, there is nothing more annoying when a developer turns to you and says, “I cannot reproduce this bug you have raised”. From my experience, this has been down to not enough accurate information for them to reproduce the bug in the first place.

I would be interested to know other people’s approaches to bug reporting as I know it can be a extremely varied from one person to another and from one company to another.

Leave a Reply