Skip to main content

Betting in Testing

“I’ve completed my testing of this feature,

and I think it's ready to ship”

“Are you willing to bet on that?”

No, Don't worry, I’m not going to list various ways you could test the feature better or things you might have forgotten.

Instead, I recommend you to ask yourself that question next time you believe you are finished. 

Why? It might cause you to analyse your belief more critically. We arrive at a decision usually by means of a mixture of emotion, convention and reason. Considering the question of whether the feature and the app are good enough as a bet is likely to make you use a more evidence-based approach.

Image result for gambling
Testing is gambling with your time to find information about the app.

Why do I think I am done here? Would I bet money/reputation on it? I have a checklist stuck to one of my screens, that I read and contemplate when I get to this point. When you have considered the options, you may decide to check some more things or ship the app. Either could be the right decision.

Then the app fails…

The next day you log on and find that the feature is broken. It turns out the programmer and you had missed the bug.

Firstly, before you beat yourself up, you may have made the right decision. Even though the feature was broken - it may have been appropriate to test the way you did.

Or it may be that you need to update your checklist, skills, or automated tests etc.

How could I fail to catch the bug and yet have made the right decisions?
  1. You and the rest of the team made choices on the best information you had available. You stopped and thought about what was the right thing to do. Based on that decision you shipped.
  2. As you could not test all the behaviours/permutations that the app was subject to, you made an educated guess based on the data available. You used an approach that suited the system as you knew it, and you would make the same decision again.

Assuming that you made the wrong choice because it had the wrong outcome is called Resulting. It is similar to the hindsight bias and can change our future views and behaviour. 


If the chance of the app failing was 0.1% (in reality we can’t usually place % on these things, but for the sake of argument...) then we might have been able to ship 1000 times and likely only seen that sort of bug once. If that’s the sort of risk profile our Product Owner is happy with, then we made the right call.

It could have been a greater risk to the business to not have that feature deployed. (Think regulatory deadlines, rival product launches etc) 

In summary, every time you test, you are gambling with your time. You can use your knowledge and expertise to help make the right bets. Sometimes those bets don’t pay off.

You may miss a bug because you need to update your checklists, skills, knowledge or automated tests. Or it could be that you made a judgement call that is right 99.99% of the time, but just not that time and your test approach was correct.

Thinking this way can help focus your work on productive and valuable behaviours. For example, We won’t panic and write too many automated tests, slowing down our team’s delivery schedule. Or we may decide to examine the impact of the code change failing, rather than just looking at IF it is failing. Will it just affect a low priority system? Or will it have a catastrophic effect?


  1. It has to be said, though, that if your company is putting the responsibility on you as a tester to declare a product "ready to ship", then they are loading you with a responsibility that you should not have. Given that no software is ever guaranteed to be 100% bug-free, there is always the likelihood that an unforeseen problem will emerge after shipping; under this scenario, the company will blame you for it when it was not your fault. Putting pressure on a tester to declare a product ready to ship is almost a self-fulfilling prophecy, given that you are being treated as a gatekeeper and presumably being put under pressure to make the earliest possible release date.

    Signing off a release is a business decision that needs to be taken by a product owner or other senior person who is of sufficient status in the company to take that decision. As a tester, the best you can do is to advise the PO that you have been unable to find obvious major defects in the time available. The decision to ship is way above your pay grade (if you are not in the actual management chain itself), and if your company still believes these things, then you have some way to go over actually teaching your company what testing is about.

    1. i absolutely agree with your point - Testers should not be asked to give "sign off" for the release. if it is happening, they have just made a scapegoat for any failure at their end.

  2. Appreciating the time and exertion you put into your blog and definite data you offer. If you love to play Satta Matka then MatkaGuru is the one of the best Matka site which provides a live result update of Satta matka. Visit here kalyan matka open for more.

  3. This is unfathomably instructive substance and framed well for a change. It's beguiling to see that a few people notwithstanding everything see how to frame a quality post. online casino betting Singapore


Post a comment

Popular posts from this blog

A h̶i̶t̶c̶h̶h̶i̶k̶e̶r̶'s̶ software tester's guide to randomised testing - Part 1

Mostly Harmless, I've talked and written about randomisation as a technique in software testing several times over the last few years. It's great to see people's eyes light up when they grok the concept and its potential. 
The idea that they can create random test data on the fly and pour this into the app step back and see what happens is exciting to people looking to find new blockers on their apps path to reliability.
But it's not long before a cloud appears in their sunny demeanour and they start to conceive of the possible pitfalls. Here are a few tips on how to avert the common apparent blockers. (Part 1) Problem: I've created loads of random numbers as input data, but how will I know the answer the software returns, is correct? - Do I have to re-implement the whole app logic in my test code?
Do you remember going to the fun-fair as a kid? Or maybe you recall taking your kids now as an adult? If so then you no doubt are familiar with the height restriction -…

DevOps and Software Testing.

Most of my recent work has been with DevOps teams. While in one sense DevOps is another evolution in software development. It also introduces some new skill requirements and responsibilities into the daily routine of a tester.

I've created a short video to highlight some of these changes and the opportunities they bring. It's not an exhaustive view of DevOps but it gives a highlight of what you could be working with.

While DevOps isn't a panacea to our software development problems, I have found that empowering teams with the ability to build and use the tools they need, can rapidly improve team morale and productivity.