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. 

Example:


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?

Comments

  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.

    ReplyDelete
    Replies
    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.

      Delete
  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.

    ReplyDelete
  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

    ReplyDelete
  4. Thanks for sharing this article here about the sports betting. Your article is very informative and I will share it with my other friends as the information is really very useful. Keep sharing your excellent work.Online Sports Betting Community in Singapore. keep sharing.

    ReplyDelete
  5. I certainly appreciate this. It is an extraordinary site and has a pleasant article. Great job! You all do an extraordinary blog, Keep up the great work.top betting site philippines

    ReplyDelete
  6. Hal terakhir yang Anda butuhkan saat bertaruh pada pertandingan sepak bola adalah meletakkan semua telur Anda dalam satu keranjang. Anda harus menemukan beberapa taruhan yang Anda suka dan menyebarkan uang Anda saat bertaruh. Ini meningkatkan peluang Anda untuk menang secara signifikan. Ketika satu taruhan kalah, yang lain menang, dan terkadang mereka berdua bisa menang. bandar togel maya

    ReplyDelete
  7. Extremely useful information which you have shared here about betting. This is a great way to enhance knowledge for us, and also beneficial for us. Thank you for sharing an article like this. singapore online betting

    ReplyDelete
  8. I truly value your work which you have shared here. The article you have shared is extremely enlightening and the focuses you have referenced are exceptionally useful. Much obliged to you for sharing this post. hasil toto 4d malaysia hari ini

    ReplyDelete
  9. Such a useful blog with required information. Thanks for sharing this amazing blog.
    AWS Certification in Chennai
    DevOps Course in Chennai

    ReplyDelete
  10. You have Shared great content here about singapore betting account. I am glad to discover this post as I found lots of valuable data in your article. Thanks for sharing an article like this.

    ReplyDelete
  11. You have a genuine capacity to compose a substance that is useful for us. You have shared an amazing post about online betting SingaporeMuch obliged to you for your endeavors in sharing such information with us.

    ReplyDelete
  12. After a long time, I read a very beautiful and very important article that I enjoyed reading. I have found that this article has many important points, I sincerely thank the admin of this website for sharing it. Get for more information best betting sites in india

    ReplyDelete
  13. Hey what a brilliant post I have come across and believe me I have been searching out for this similar kind of post for past a week and hardly came across this. Thank you very much and will look for more postings from you Get for more information cricket bet sites in india

    ReplyDelete
  14. This information is meaningful and magnificent which you have shared here about the Game. I am impressed by the details that you have shared in this post and It reveals how nicely you understand this subject. I would like to thanks for sharing this article here.Real Fixed Matches Site.

    ReplyDelete
  15. Thanks for Sharing Information to us. If Someone wants to know about Top Software testing Companies this is the Right place for you!

    ReplyDelete
  16. After a long time, I read a very beautiful and very important article that I enjoyed reading. I have found that this article has many important points, I sincerely thank the admin of this website for sharing it. Get for more information https://goldenexch.co/

    ReplyDelete
  17. A very delightful article that you have shared here. Your blog is a valuable and engaging article for us, and also I will share it with my companions who need this info. casino night Thankful to you for sharing an article like this.

    ReplyDelete
  18. This comment has been removed by the author.

    ReplyDelete
  19. This post is so useful and valuable to increase our knowledge. I am happy that you have shared great info with us. 3webet real online betting Grateful to you for sharing an article like this.

    ReplyDelete
  20. This field is risky because many people have lost their money because they had not much experience about betting. They should consult with seniors or learn some experience and then join this field. I hope, through this, they will earn some money. Dissertation proposal help.

    ReplyDelete
  21. I’ve been surfing online more than 3 hours today, yet I never found any interesting article like yours. It is pretty worth enough for me. Personally, if all webmasters and as you did, the web will be a lot more useful than ever before. Best of luck for the next! Please visit my web site sonebet.com. Best Sports Betting Singapore service provider.

    ReplyDelete
  22. Extremely useful information which you have shared here. This is a great way to enhance knowledge for us, and also helpful for us. Thankful to you for sharing an article like this. online casino sg

    ReplyDelete
  23. I am very thankful to you that you have shared this great information with us. Here I find some different kind of knowledge, and it is useful for everyone. Thanks for share it.D&D Dice

    ReplyDelete
  24. Aw, this was a really nice post! I would like to thank you for the efforts you’ve put in writing this site. Best of luck for the next! Please visit my web site sonebet.com. Best Singapore Football Betting service provider.

    ReplyDelete

Post a Comment

Popular posts from this blog

The gamification of Software Testing

A while back, I sat in on a planning meeting. Many planning meetings slide awkwardly into a sort of ad-hoc technical analysis discussion, and this was no exception. With a little prompting, the team started to draw up what they wanted to build on a whiteboard. The picture spoke its thousand words, and I could feel that the team now understood what needed to be done. The right questions were being asked, and initial development guesstimates were approaching common sense levels. The discussion came around to testing, skipping over how they might test the feature, the team focused immediately on how long testing would take. When probed as to how the testing would be performed? How we might find out what the team did wrong? Confused faces stared back at me. During our ensuing chat, I realised that they had been using BDD scenarios [only] as a metric of what testing needs to be done and when they are ready to ship. (Now I knew why I was hired to help) There is nothing wrong with c

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. These diagrams tend to confuse people, hence the video... 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.