tag:blogger.com,1999:blog-8951904624959546499.post5047942456150807981..comments2008-09-07T08:30:33.664-04:00Eric Jacobsonhttp://www.blogger.com/profile/08216361684596485033noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8951904624959546499.post-57404701712487057122008-09-06T12:42:00.000-04:002008-09-06T12:42:00.000-04:00I think this also provides the testers with the chance to learn from the bugs that they've missed.green2noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-83214586619818221232008-09-03T19:28:00.000-04:002008-09-03T19:28:00.000-04:00Agree....<BR/><BR/>If someone outside the department considers some behavior of the program to be a bug, even if they can’t explain it in detail, I would prefer they submit it. And I have no problem with other people doing so. Ultimately the customer is who I am out to please. One less bug in the field is one less bug they have to deal with.Michele Smithhttp://www.blogger.com/profile/05639189538178022310noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-66261349072552661302008-09-03T05:38:00.000-04:002008-09-03T05:38:00.000-04:00Certainly agree. In my experience the bugs written by non-testers can be invaluable.<BR/><BR/>Sure you need to decipher them and some are plain wrong. But even those are an insight into how usable the software is(n't), what may need to be added to a help file or even reveal a whole new raft of tests that could be run.Mark Crowtherhttp://www.blogger.com/profile/11540303029361604504noreply@blogger.com