A weekly source of software testing news
ISSUE #76 - October 28, 2018
Apropos the upcoming Halloween, our scary topic today is bugs and how to deal with them: from writing bug reports and reporting duplicates to dealing with defect clustering and deciding what percentage of bugs to address.
On viewing bug reports as “quality offers” whose aim is to improve quality of the product – which, of course, is the whole point of filing bugs, but this post suggests a positive way of thinking and writing:
https://thelifeofoneman.com/turn-bug-report-quality-offer
When should bugs be reported individually even if they seem to have the same root cause, and could therefore be called duplicates?
https://www.stickyminds.com/article/when-testers-should-consider-bug-duplicate
On defect clustering and how to turn it from a problem into a solution:
https://www.rainforestqa.com/blog/2018-04-25-defeat-defect-clustering/
Decent intro to writing a bug report. Sadly, examples are only for login, which I tend to view as too simple to be insightful, but gotta start somewhere.
https://medium.com/@Haje/how-to-write-the-perfect-bug-report-6430f5a45cd
Not all bugs are worth fixing - set a target stability rate the same way you do for site availability:
https://blog.bugsnag.com/application-stability-monitoring/
Tragicomic story from an unnamed company that lost user content through a rollout/rollback of a feature that… ah, you just gotta read it.
https://rachelbythebay.com/w/2018/10/05/recipes/
If this wasn’t scary enough, dip into our older bug-themed issue from last Halloween:
http://testersdigest.mehras.net/2017/10/28/testers-digest-36-scary-bugs.html
If you received this email directly then you’re already signed up, thanks! Else if this newsletter issue was forwarded to you and you’d like to get one weekly, then you can subscribe at http://testersdigest.mehras.net
If you come across content worth sharing, please send me a link at testersdigest@mehras.net