tag:blogger.com,1999:blog-5948141587422980338.post8019239311903093507..comments2023-07-29T14:44:21.646+02:00Comments on The Tester's Headache: Risk Compensation and AssumptionsSimon Morleyhttp://www.blogger.com/profile/10629592766073538811noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5948141587422980338.post-2883299100178998932010-12-19T18:24:58.524+01:002010-12-19T18:24:58.524+01:00@Darren,
I missed the assumption angle in the rep...@Darren,<br /><br />I missed the assumption angle in the reply - yes, there is a danger there. Here, I think it's important to keep thinking (or asking questions) about the subject and what's needed - even questioning the "up front tests" and "show and tell" - from yours and the devs perspectives.Simon Morleyhttps://www.blogger.com/profile/10629592766073538811noreply@blogger.comtag:blogger.com,1999:blog-5948141587422980338.post-35153431526198858232010-12-19T18:10:18.536+01:002010-12-19T18:10:18.536+01:00Hi Darren,
Yes, good angle, but the fact it's...Hi Darren,<br /><br />Yes, good angle, but the fact it's worked so far is no guarantee it will carry on working :) <br /><br />Your "show and tell" and "up front tests" could be incorporating feedback into both the coder and tester mindsets - and that's important! <br /><br />It's when we slow or reduce that feedback loop from/to our test activities that there's a danger of falling into this trap.<br /><br />Thanks for the comments!Simon Morleyhttps://www.blogger.com/profile/10629592766073538811noreply@blogger.comtag:blogger.com,1999:blog-5948141587422980338.post-66385135483352582022010-12-19T17:12:10.164+01:002010-12-19T17:12:10.164+01:00Hi Simon,
I've been neglecting my Google Read...Hi Simon,<br /><br />I've been neglecting my Google Reader so sorry for the late reply :-)<br /><br />Firstly, what an excellent post! Seriously, I very much enjoyed reading this.<br /><br />A good example I can provide from my workplace is a type of testing in itself "Proactive Testing" (http://www.bettertesting.co.uk/content/?p=123) which as you've read previously relies currently upon two main techniques to prevent defects appearing in the code base. <br /><br />One of these techniques "Up front test cases" & to a lesser extent "Show and tells" provide a high risk that the developers original test thoughts will be lost from the execution of these techniques. Now this may be okay for some dev's who care less about testing & swing on using their test team as a safety net, however for those that generally do excellent testing already we run a high risk of losing those test idea's by presenting them with our own.<br /><br />Luckily for us so far this has worked fantastically & has had the reversed effect in getting developers more interested in their own test ideas. However like anything that’s placed into a working model it runs the risk of having negative side effects.<br /><br />Thanks for sharing Simon.<br /><br />Cheers,<br /><br />Darren.Darren McMillanhttp://bettertesting.co.uknoreply@blogger.com