By bloid
via softarc.blogspot.com
Published: Mar 16 2008 / 19:15
One of the first lessons, hard lessons, you learn coming into the world of software development out of college is how hard it can be to understand bug reports.
Variously they can be vague, misleading, inaccurate, confusing or best of all - misunderstanding a feature for a bug (the latter often points to usability issues).
Having endured many of these and now doing a fair bit of testing of my current application, I try to "be the change I wish to see in the world". So I've come up with the following scheme for bug reports.
Comments
hal10001 replied ago:
Great idea for a post, but there is one small piece missing, and that is for those that do not have an "official" QA department. I work at a company where we are responsible for our own QA, and our customer service and marketing folks tend to find the bugs with the more difficult to replicate scenarios. They have a very hard time explaining these issues, and how they might be duplicated. Be sure they are also in the loop with this process -- it is a great way to eliminate confusion.
Voters For This Link (20)
Voters Against This Link (2)