[Software Testing Club Blog | Oct 6 2011 | myself ]
All oracles are fail-able to a certain level of confidence.
Recently I had the opportunity to participate in the acclaimed dice game. I also had the chance to be game master on a variation of the dice game session for a small test team. Reflecting on the experiences I had two considerations: (Some spoilers apply)
When are you confident enough?
The dice game is played by a loop of theories/ideas and tries/tests on the idea. The goal is to produce a theory/algorithm that can successfully predict the number that the game master presents. How many tries/tests/checks would give you confidence in the theory you have in mind? Options:
- When you successfully predict one throw. Ie you say 7, game master say 7. Do you yell “LOOSERS, Sea ya”?
- When you have 7 successfully predicted in a row? (why 7)
- All 7776 combinations of 5 pieces of 6-sided one-colored standard dices?
- Do you try every throw just once, or more times?
- Would you know if every trial number divisible by 100, the game master would say “pi” (think leap years)
The dice game seems simple, but the problem domain of even the dice game is infinite. Or at least practically infinite (7776 is practically infinite in the dice game IMHO). The number of tests doesn’t matter, but the character of the test, relative to your mental models, matters a great deal. My purpose is not to find a fixed number of tries, but to make you consider the underlying assumption on confidence levels. That is you have a confidence in your model until it fails. You are confident to the level of x successful predictions, where the x+1 prediction fails. All you know at that time is that your theory is “incomplete” (not wrong, not right) – and this calls for more learning and more ideas…
All oracles are failable
The oracle in software projects is the ressource of answers – the documents, the mindmap, the subject matter expert. In the dice game the game master is the oracle. We are humans hence failable. The physical oracles (docs, …) even more. This made me ponder:
- Would you approach the dice game differently actively knowing that the dice game master is failable?
- If the game master (aka oracle) made a deliberate error ever once in a while – would you know?
- If there is a bug (non deliberate) in the game masters algorithm would you know?
- How would you test for the oracle making mistakes?
- Do you test the dice game different if it was a human or machine oracle
- First think about the dice game being computer based
- Secondly what if it was a human behind a computer based interface
- Consider the implications of the Turing Test
- Oh, did you forget that I could make mistakes? – was that a rule, or an assumption?
The key framing of the dice game is usually a lesson in learning, in theory setting and trials of that theory – still under the underlying assumption that the game master can deal with any test that is offered. What would happen if the game master was blindfolded? What would the case if the algorithm was more complex – less humanly processable in a short time. There will always be a level of capability of the oracle, and it will fail – eventually.

[…] Testing a new version All oracles are failable […]
LikeLike
[…] at my SoftwareTestingClub blog – more from my STC Blog here: All oracles are failable, Testing decommissioning of ICBMs and software and Testing a new […]
LikeLike
[…] product” doesn’t work, the story of apple). But remember they are people too – even oracles can be wrong, and set up a measurement that will be counterproductive. Management only focus on […]
LikeLike
[…] See also Eating wicked problems for breakfast, Even superheros need help, How to spot defects Innovation is about the unknown – deal with it My strengths All oracles are failable […]
LikeLike
[…] expected confidence. In other words ”what are you OK with?” How can we help you gain confidence in the solution? What trends should we look […]
LikeLike
“when someone tells me someone has asked them to give them confidence through testing, my simple advice to them would be this: stick to the mission.
…I believe the mission of testing is gaining information;
”
http://qualityremarks.com/the-confidence-game-what-is-the-mission-of-testing/
LikeLike
[…] See also: Establish yourself as an expert or thought leader, All oracles are fail-able […]
LikeLike
[…] or even always right. Even the best business analyst or subject matter expert may be wrong. Your best oracle may fail too. Or you may be focussing on only getting what you […]
LikeLike