ISSUE #54 - April 15, 2018
Bugs happen. How do you respond? Some thoughts on blameless approach applied to finding / not finding and fixing / not fixing bugs.
How to organize “Bug Hunts”, more commonly known as bug bashes:
What is a test team to do when they missed a bug? Good application of the blameless approach here:
To fix or not to fix, that is the question. Interesting blameless analysis of how to respond to outages, do you improve the system or leave it as is?
A particular situation when a bug should not be fixed: sometimes the user needs a way to put the system into an invalid state while recovering from a much worse invalid state.
Fun split brain scenario bug:
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 email@example.com