that really is a must-have for anybody serious about QA testing new software - I've had (very limited) experiance of being at the developer-end of testers who, quite frankly, didn't know what the fuck they were talking about. Case in point:
some years ago, I was working on a single-player standalone version of
Gang-wars and needed somebody to help me test whilst I continued development. One of the 3 people interested kept sending me emails with stuff like "your game stopped working. I loaded it and tried playing it but I got an error and it crashed"
me: what error did you get?
him: I don't remember.
me: Um, okay. What did you do right before it crashed?
him: well, I was playing it and it gave me an error message then crashed.
me:Uh huh... and what were you doing in the game, as in, what were you clicking, typing etc?
him: I don't know, I was just clicking stuff and trying to play the game
etc...
suffice to say I never finished that game :/
On the other hand, I've always tried to make useful and worthwhile bug/testing reports when i've been on a beta (*cough*selfpimping*cough*) and whilst I've not been on that many projects (the last one being a pokemon trading card video game about 2 years ago) I did my best to send a bi-daily bug report of what i've found, along with screenshots of the problems, and/or information on how to recreate the errors. even if I didn't find anything, I'd let them know what i'd been doing, and add my suggestions for the program.
That kinda stuff,