What Makes a Bad Bug Report?

Bugs are the lifeblood of a beta test and it’s what our clients want when you test a product. They have enlisted your help because they want to make certain they deliver the best quality product to the public. But a test with 50 testers can results in hundreds of bugs, which can be a lot to sift through. So, when you submit a bug, you need to make sure it’s a good one. Good bugs are real, detailed, and complete. But, what is a bad bug?

A bad bug is an issue that doesn’t tell us anything. It raises more questions than it answers and consumes a lot of our time as we try to determine what you’re trying to tell it. This slows down the test and keeps us from getting your feedback to the client. So, what makes a “bad” bug?

They’re incomplete

We need to know as much as you can share about your issue. If your bug is unique, you should give us much detail as you can. One line saying “it’s not working” means nothing to us. Make sure you give us as complete a picture as possible about what happened before, during, and after the problem, so we have the best shot at reproducing and addressing the problem.

They’re hard to read

Spelling errors, ALL CAPS, and poor English make a bug report confusing and even frustrating to read. We know every user isn’t Shakespeare but we do hope everyone tries to write clearly. The clearer the bug, the faster we can respond.

They’re redundant

Our system is a collaborative environment in which you can contribute to issues others testers have reported. If you see a bug that’s similar to what you experienced, you can vote it up and add your comments. You don’t get extra points for submitting your own bug report. If we get duplicates, they are going to be filed under the first bug report anyway.

They’re emotional

We know you can frustrated when you have a problem. However, calling a product bad or putting a lot of anger or emotion into your report isn’t helpful. Keep to the facts in bug reports and share your emotions in surveys and journals instead.

They aren’t actually bugs

Before logging any bug, you should be certain you haven’t done something wrong, misread the instructions, or simply missed something. There is no shame in making a mistake.

They’re feature requests

If something doesn’t work the way you want it to or doesn’t come in the color you like, our client needs to hear that. However, those aren’t bugs. If you have an idea for a change or improvement, log it as a feature request instead. Bug reports are other for problems or mistakes you run into while using the product.

Writing good bug reports can help you stand out as a quality tester in our projects, which will help you get into future projects. So take the extra time to make sure each bug you submit is clear and relevant, and happy testing!

Not a Betabound community member yet? Sign up now!