I am giving a talk on how to write a good bug report. Now, like me you probably only ever write really good, full and insightful bug reports......but, you might have come across some really bad reports, you know the sort of thing... " I just tried to save a new person record and it didn't work properly". (Yes, that really is the full text from a bug report on one of my projects I am ashamed to say)
If you have any real life example of bad bug reports you could share with me as examples I would be most grateful. You don’t have to name names (fun though that is), but if you could put a little context around the report that would help. i.e.
The project was a CRM system and one of the main features was a very rich and powerful system to allow you to link new contacts (person records) with various departments within the organisation, and in so doing give them a tailored set of information. One tester submitted the following bug as a high priority bug.
" I just tried to save a new person record and it didn't work properly".
Many thanks in advance for your help.
I see far too many of (2) and (5).
It's not easy to test the fix for a bug if it's not clear what circumstances caused the original bug to appear. Performance issues without any metrics or techie bugs which don't even tell you what business scenario is affected are particular bugbears of mine.
This happened where I work recently. I kept getting a load of bug reports of the "this doesn't work" calibre, and then a couple of weeks in she asked what the URL was for the testing server (the one where she was meant to be looking at to test) Yep, she'd been looking at the wrong server the entire time, despite it being the main testing server for (and only server for this site for the most part of several) months.
I feel that pain...
Come on, clearly the message was stupid! You should've taught it a thing or two!