tag:blogger.com,1999:blog-736810000699453506.post2555812396179523555..comments2023-05-11T00:49:36.314-07:00Comments on Ruminations on Computing: Why We Conduct Bug BashesSteve Rowehttp://www.blogger.com/profile/17905356014908630180noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-736810000699453506.post-61703745303054688712009-02-13T06:29:50.000-08:002009-02-13T06:29:50.000-08:00Hi Steve,I agree with your experience, I've be...Hi Steve,<br>I agree with your experience, I've been running and recommending Bug Hunts for the past 6 or 7 years and I always find that even if Management is usually skeptic at the beginning of the process they are bought over by the value the Organization gains with these activities.<br>I'd add 2 things to your observations:<br>1. My experience with hunts is to do them as a Pair-Testing exercise, and we involve the product developers in it as well. This brings up bugs and scenarios that are seldom achieved by testers working independently.<br>2. An additional added value to these activities is that the Organization gains a better perspective about what testing is about and we tend to gain more respect about what we do and how we do it.<br>I wrote some additional pointers to the stuff I've doing in here: http://blog.practitest.com/2008/05/what-do-you-pack-when-you-go-for-bug.html<br>In any case, its good to see that other people believe in these unconventional approaches. Maybe in time they will also become mainstream :)Joel Montveliskyhttp://blog.practitest.comnoreply@blogger.comtag:blogger.com,1999:blog-736810000699453506.post-24748349273985550462009-02-13T12:09:32.000-08:002009-02-13T12:09:32.000-08:00Thanks for the additional Joel. I hadn't cons...Thanks for the additional Joel. I hadn't considered doing these as a joint exercise between test and dev. That would be very interesting.SteveRowenoreply@blogger.comtag:blogger.com,1999:blog-736810000699453506.post-22416806570993819342009-02-13T21:05:25.000-08:002009-02-13T21:05:25.000-08:00Do you analyse the bugs found during a bug bash to...Do you analyse the bugs found during a bug bash to find out why they were't caught by 'normal' testing ?Philknoreply@blogger.comtag:blogger.com,1999:blog-736810000699453506.post-51768464083758737062009-02-16T00:01:26.000-08:002009-02-16T00:01:26.000-08:00>Do you analyse the bugs found during a bug >...>Do you analyse the bugs found during a bug <br>>bash to find out why they were't caught by >'normal' testing ?<br>this is a good question.<br>something i've seen during bug bashes is that some people will use the opportunity to finally log some annoyances that have been a gripe for a while. <br>all sorts of little grudges can come out. <br>plus -- it's a great chance to tear apart the work of that programmer who annoys you the most ;-)<br>and definitely involving the whole team gives devs a better understanding of testing. (not a complete understanding, but... a better one than we had before)<br>lbsecretGeekhttp://secretGeek.netnoreply@blogger.comtag:blogger.com,1999:blog-736810000699453506.post-12610053797350780802009-02-17T19:13:49.000-08:002009-02-17T19:13:49.000-08:00Hi Steve,We (SAP Portal Platform) call that "...Hi Steve,<br>We (SAP Portal Platform) call that "QA Days", and like Joel, we usually have Dev with us as well.<br>One problem with such events is the mass of duplicate bugs, of course we narrow that down by assigning different areas / scenarios to different testers but still we see a lot of duplications which requires thorough investigation of the duplication before we file the right bugs in the system.<br>How do you tackle that?<br>AsafAsaf Saarhttp://www.asaf.co.ilnoreply@blogger.com