Skip to main content

The Test in Test Match


There are times when getting a stakeholder to agree that there's a problem is not easy. Then there are times where, having found a stakeholder who accepts the existence of an issue, you have difficulty persuading them that it's important to find a solution to it now.  And then there are those times when, having found a sponsor who both recognises and wants to relieve the particular headache you've identified, they can't get past some narrow view of it - either in terms of the problem space or the complexity of the necessary solution or both - and you end up with incomplete fixes that might focus on a particular case or which will fail in logic for some subset of cases and perhaps even compromise the integrity of the implementation to boot.

Limited-overs cricket found itself in this position a few years ago. In this format of cricket the two teams each bat for one innings to try to score runs given a set number of balls bowled to them and within a set number of wickets (the number of players who can be out). When all the balls are bowled or all of the wickets are lost, the innings ends. Whichever team makes the most runs wins.

Unlike many other sports, cricket matches stop during rain and, if the rain lasts long enough, the match is reduced in length to ensure that it still fits into the day.  The cricketing authorities recognised the problem - how to perform that reduction fairly - and knew they needed a solution but, by the account in Duckworth Lewis: The Method and the Men behind it, failed to comprehend the range of scenarios that needed to be considered and were not prepared to think about the problem in anything other than a single dimension.

The case that preoccupied cricket was when it rained after team 1 (the first team to bat) had finished their innings but before team 2 started, or had completed, theirs. In the case where this reduced the number of balls that team 2 could face, they would simply scale the number of runs that team 2 had to make proportional to the number of balls. So, if team 1 made 100 in their innings, and team 2 only faced half as many balls as team 1 then they'd have to make half the total (plus one to win), i.e. 51. Which seems logical enough except that it doesn't take into account that team 2 still have as many wickets as team 1 had and so can take more risks without worrying about running out of wickets.

One key insight required here is that more then one parameter determines a fair rescaling of the total: both runs and number of wickets available are important. A second is that rain could occur at any point in the match, even forcing team 1 to receive fewer balls than they expected when they started their innings, if heavy rain falls during it. The rescaling needs to be fair to both teams and so needs to take into account the point in the innings at which the match was affected: if team 1 were cautious initially to preserve wickets, with the intention of being aggressive at the end of their innings, but then the innings is cut short they will feel aggreived because they could and would have been more aggressive had they known there were fewer balls to face.

Duckworth and Lewis are academics, statisticians and cricket lovers. Their book - which can be quite dry and occasionally petty, but is worth persevering with - details the original problem and a selection of sticking plasters that were applied to it. They show how broken methodologies implemented with apparently little thought or testing resulted in severe embarrassments such as a world cup match where South Africa's innings was reduced in length but their target was not (due to the then-current rules) and so instead of needing 22 runs from 13 balls they were rescaled to 22 runs from 1 ball, which is essentially impossible in the game.

The solution they proposed, the Duckworth Lewis Method, now in operation in cricket worldwide, introduces the notion of resource for a batting team which is generated from historical match data and takes into account the match position, the number of balls still to come and the number of wickets still standing. Under this system, the relative resources available to the teams when play is interrupted are used for scaling. For example, a team with many overs and wickets in hand will have a lot of resource; a team with the same number of overs but few wickets will have less because they would likely have to play more defensively to preserve their wickets.

In the book Duckworth and Lewis demonstrate the problem by highlighting a relatively small number of realistic scenarios in which unwanted results would occur - results which it was clear to the cricketing authorities would be travesties. They use these to enforce the message that a higher level of sophistication (than simply scaling based on number of balls) is required. They suggest a solution and describe it at a high level in terms that should be already familiar to their stakeholders. They, importantly, provide an implementation of the method that would be tractable too. (And over time they have refined the methodology so that its use during a match is now relatively streamlined.)

They discuss clearly and reasonably the relative advantages and disadvantages of their methods compared to others. They explain how some of the secondary stakeholders - the media in particular - seem unwilling to try to get their heads round the principles of the solution and what they've done to try to overcome that. They identify the weak spots that still exist in certain extreme scenarios and they suggest enhancements, some of which are rejected by the cricket authorities to Duckworth and Lewis's clear frustration. They address suggestions from third parties for the application of the method in situations it was not designed for, such as Test Match cricket, where the number of overs is not limited and explore other places it could be applied or extended to. And if that's not enough, they even provide a FAQ.

Let's not get into the is testing (a) science debate  here (although if you're interested...) but instead look at some relevant parallels with a testing role and the way that Duckworth and Lewis went about their business:
  • they analysed approaches using thought experiments and real data searching for the anomalous cases - cases not presented to them as problems by the stakeholders 
  • they communicated with their stakeholders and others in their own language to a relevant and realistic level of detail
  • they were and are open about their own approach and to other approaches, wanting to judge them all on a level playing field.
Image: http://flic.kr/p/6Pzxej

Comments

Popular posts from this blog

Can Code, Can't Code, Is Useful

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested in your working context and the way

Testing (AI) is Testing

Last November I gave a talk, Random Exploration of a Chatbot API , at the BCS Testing, Diversity, AI Conference .  It was a nice surprise afterwards to be offered a book from their catalogue and I chose Artificial Intelligence and Software Testing by Rex Black, James Davenport, Joanna Olszewska, Jeremias Rößler, Adam Leon Smith, and Jonathon Wright.  This week, on a couple of train journeys around East Anglia, I read it and made sketchnotes. As someone not deeply into this field, but who has been experimenting with AI as a testing tool at work, I found the landscape view provided by the book interesting, particularly the lists: of challenges in testing AI, of approaches to testing AI, and of quality aspects to consider when evaluating AI.  Despite the hype around the area right now there's much that any competent tester will be familiar with, and skills that translate directly. Where there's likely to be novelty is in the technology, and the technical domain, and the effect of

Testers are Gate-Crashers

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Testers are the gatekeepers of quality" Instinctively I don't like the sound of that, but I wonder what you mean by it. Perhaps one or more of these? Testers set the quality sta

Am I Wrong?

I happened across Exploratory Testing: Why Is It Not Ideal for Agile Projects? by Vitaly Prus this week and I was triggered. But why? I took a few minutes to think that through. Partly, I guess, I feel directly challenged. I work on an agile project (by the definition in the article) and I would say that I use exclusively exploratory testing. Naturally, I like to think I'm doing a good job. Am I wrong? After calming down, and re-reading the article a couple of times, I don't think so. 😸 From the start, even the title makes me tense. The ideal solution is a perfect solution, the best solution. My context-driven instincts are reluctant to accept the premise, and I wonder what the author thinks is an ideal solution for an agile project, or any project. I notice also that I slid so easily from "an approach is not ideal" into "I am not doing a good job" and, in retrospect, that makes me smile. It doesn't do any harm to be reminded that your cognitive bias

Play to Play

I'm reading Rick Rubin's The Creative Act: A Way of Being . It's spiritual without being religious, simultaneously vague and specific, and unerring positive about the power and ubiquity of creativity.  We artists — and we are all artists he says — can boost our creativity by being open and welcoming to knowledge and experiences and layering them with past knowledge and experiences to create new knowledge and experiences.  If that sounds a little New Age to you, well it does to me too, yet also fits with how I think about how I work. This is in part due to that vagueness, in part due to the human tendency to pattern-match, and in part because it's true. I'm only about a quarter of the way through the book but already I am making connections to things that I think and that I have thought in the past. For example, in some ways it resembles essay-format Oblique Strategy cards and I wrote about the potential value of them to testers 12 years ago. This week I found the f

Meet Me Halfway?

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answer would be almost meaningless and certa

Test Now

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "When is the best time to test?" Twenty posts in , I hope you're not expecting an answer without nuance? You are? Well, I'll do my best. For me, the best time to test is when there

Rage Against the Machinery

  I often review and collaborate on unit tests at work. One of the patterns I see a lot is this: there are a handful of tests, each about a page long the tests share a lot of functionality, copy-pasted the test data is a complex object, created inside the test the test data varies little from test to test. In Kotlin-ish pseudocode, each unit test might look something like this: @Test fun `test input against response for endpoint` () { setupMocks() setupTestContext() ... val input = Object(a, OtherObject(b, c), AnotherObject(d)) ... val response = someHttpCall(endPoint, method, headers, createBodyFromInput(input) ) ... val expected = Object(w, OtherObject(x, y), AnotherObject (z)) val output = Object(process(response.getField()), otherProcess(response.getOtherField()), response.getLastField()) assertEquals(expected, output) } ... While these tests are generally functional, and I rarely have reason to doubt that they

A Qualified Answer

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn ,   Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Whenever possible, you should hire testers with testing certifications"  Interesting. Which would you value more? (a) a candidate who was sent on loads of courses approved by some organisation you don't know and ru

README

    This week at work my team attended a Myers Briggs Type Indicator workshop. Beforehand we each completed a questionnaire which assigned us a personality type based on our position on five behavioural preference axes. For what it's worth, this time I was labelled INFJ-A and roughly at the mid-point on every axis.  I am sceptical about the value of such labels . In my less charitable moments, I imagine that the MBTI exercise gives us each a box and, later when work shows up, we try to force the work into the box regardless of any compatiblity in size and shape. On the other hand, I am not sceptical about the value of having conversations with those I work with about how we each like to work or, if you prefer it, what shape our boxes are, how much they flex, and how eager we are to chop problems up so that they fit into our boxes. Wondering how to stretch the workshop's conversational value into something ongoing I decided to write a README for me and