Percentages from the last "bug bash"

We had a "bug bash" on some sync features in OneNote last week.  I thought it may be interesting to look at the resolution of the bugs we found since I mentioned that some of the bugs reported in these situations may duplicates of each other and things like that.

 (Please don't read too much into this.  These stats are merely the result from one single test effort over the course of 2 days of testing and may not be indicative of any other statistics from other teams.)

 After the two days of testing, we had 14 reported bugs.  4 of them - 28% - have already been closed.  We had an inconsistent server configuration and that led to some noise when we first started.  Once we investigated the server, we figured out we had not set it up correctly, but by then these bugs had already been entered.  Obviously, we need to get setup working (and we will!) and we simply got these bugs off our radar.

 One bug was resolved as a duplicate to a pre-existing bug.  That's 7%,albeit only a single bug report.

Another bug has to do with a missing icon.  We handed that off to our designer team and linked our bug to theirs.  Look and feel is important and we will ensure the icon is correct once it gets checked into our codebase.

The other 8 bugs are still being tracked and have been handed to developers. 

So during the bash, 42% of these bugs have already been closed.  58% of them bear further investigation and we are looking through logs, reproducing ("repro-ing," in the lingo) the bug reports and testing proposed fixes for them. 

Overall, I was pretty happy with the percentages we saw with our bug reports.  Bashes produce results that can be all over the map and anything over a 50% rate that are not duplicates, noise, etc... seems like a success to me.

Questions, comments, concerns and criticisms always welcome,
John