Posted on Thursday 3 November 2005 - Popularity: unranked
If you’re a developer of public software, then bug reports are something extremely important. Reports that say something on the line of “It doesn’t work!”, reports that just make no sense, reports that don’t give enough information or even reports that give completely wrong information … all that is just taking away time you could have used to add an other feature.
Now of course there are always two sides of a story, an application that makes it hard to report bugs or a beta tester that doesn’t know how to report bugs. While the following article wont help you much on the software side of the problem, it gives some important in-depth advice for beta testers how to report bugs effectively. So definitely let your beta testers read through this article first if you plan to use your time useful.
