Skip to main content

Ask a Stupid Equestrian

I soon decided, when asked to contribute the first A day in the life... column for our new internal company newsletter, that my daily grind in words wasn't very interesting. So I wrote this instead, based heavily on Iain McCowatt's excellent blog post (which is part of my team's recommended reading) Spec Checking and Bug Blindness used here with his kind permission.

One day

So this horse walked into a pub. "Why the long face?" asked the chap behind the bar. The horse died a little inside and then said "I've been testing software all day."

"Testing?" the barman chortled, "isn't that just making sure the thing does what it's supposed to?"

The horse bridled at that and trotted away to an empty table where it picked up a pile of beer mats. Back at the bar it arranged three of them into a trefoil, each mat overlapping both of the others. It looked the barman in the eye.

"You can think of it this way," it started. "There's the things we need to do" and it jabbed a fetlock at the first mat, "the things we specified we would do," a point at the second, "and what we implemented," and a final poke at the third mat.

"Hmm ... drink?"


"Red or white?"

"Got any Eck?"

"Eck wine?"

Silence for a moment. The horse raised its eyebrows slightly. The barman pulled a long face and the horse turned back to the mats.

"So the bit where all three overlap, that's where you might imagine the tester does his or her work: we needed it, we planned to do it, we built it, now just check it before we ship it."
It glanced up, "I'll have rum. A treble". The barman wasn't falling for that one... again. He reached under the counter for a glass but saw the horsing shaking its head slowly back and forth so he grudgingly picked a gold cup from a shelf near the optics.

There was no-one else in the place, so the barman put the drink down without moving away. It looked like he was saddled with the horse for the time being. Mistaking stationary for still interested, the horse continued. "Checking that the software does what the spec says could confirm some of that stuff but otherwise it’d find mostly things that we'd said we wanted but hadn't done or had done but done wrong."
"Hmm" the barman said, wondering whether he could check his Facebook without the horse noticing.

"What about finding things that we needed to do but didn't do? We can't find all of those by checking items off the spec and you can bet that there'll be some" and it waved its cup towards the first mat. "And some of them we mightn't even know we needed to do."
"Hmmnmmnn?" the barman said distractedly, deciding that probably he couldn't.

But the horse had got the bit between its teeth now, "and then there's the things that we've implemented that we didn't ask for." The third mat. "Sometimes that's good - we might end up with a bit of extra useful functionality. But we might also have done some stuff we didn't want to do, like changing existing behaviour somewhere else in the product, and we've only got a limited amount of time to look for it, so how should we go about it?"
It stared at the barman who was having a mare. Still no other punters.

"And then we might have implemented stuff that wasn’t needed. It might be in the spec – or not - but it turns out that it's the wrong thing to do anyway. Perhaps customers don't want that. Perhaps it interacts badly with something else, perhaps ... " and it stopped and dropped its head as it gestured in the general direction of the third mat again, a tear in its eye " ... where's the manual for finding that, eh?"
"Time for you to get on your way, I think" said the barman, walking round to the horse and (infeasibly, but no more so than a horse holding a cup and drinking rum) putting his arm round its shoulders to give it a hand.

"And as for stable builds ..." but from long experience the barman knew it ill behooved him to let the horse get on to that so he ushered it towards the door and turfed it out.



The following day

So this horse walked into a pub. "Why the long face?" asked the chap behind the bar.

Silence for a moment. The barman raised his eyebrows slightly. The horse raised its eyebrows slightly.


  1. Reminds me of slides 50 + 51 of the RST course (

  2. @Chris: You're right. I guess the motivation is similar: to highlight that testing can be a broader activity than many people realise (some testers included).

  3. The 'Required/designed/delivered' trichotomy appeared in my 1993 paper, "A Unified Approach to System Functional Testing" for the first Eurostar conference.

    Coincidentally, there are also big hints at using examples (I called them behaviours) to validate requirements and double as test cases. Nowadays, we'd call that Behaviour-Driven Requirements :O)

  4. @Paul: Good shout. The core idea in the Pawnbrokers Model is essentially the same as here. Did you develop it any further outside of that paper?

  5. Afraid not. It was a bit of fun really, but the overlapping and underlapping(?) Sets trigger interesting questions e.g. Required, not designed, delivered?


Post a Comment

Popular posts from this blog

Notes on Testing Notes

Ben Dowen pinged me and others on Twitter last week , asking for "a nice concise resource to link to for a blog post - about taking good Testing notes." I didn't have one so I thought I'd write a few words on how I'm doing it at the moment for my work at Ada Health, alongside Ben. You may have read previously that I use a script to upload Markdown-based text files to Confluence . Here's the template that I start from: # Date + Title # Mission # Summary WIP! # Notes Then I fill out what I plan to do. The Mission can be as high or low level as I want it to be. Sometimes, if deeper context might be valuable I'll add a Background subsection to it. I don't fill in the Summary section until the end. It's a high-level overview of what I did, what I found, risks identified, value provided, and so on. Between the Mission and Summary I hope that a reader can see what I initially intended and what actually

Why Do They Test Software?

My friend Rachel Kibler asked me the other day "do you have a blog post about why we test software?" and I was surprised to find that, despite having touched on the topic many times, I haven't. So then I thought I'd write one. And then I thought it might be fun to crowdsource so I asked in the Association for Software Testing member's Slack, on LinkedIn , and on Twitter for reasons, one sentence each. And it was fun!  Here are the varied answers, a couple lightly edited, with thanks to everyone who contributed. Edit: I did a bit of analysis of the responses in Reasons to be Cheerful, Part 2 . --00-- Software is complicated, and the people that use it are even worse. — Andy Hird Because there is what software does, what people say it does, and what other people want it to do, and those are often not the same. — Andy Hird Because someone asked/told us to — Lee Hawkins To learn, and identify risks — Louise Perold sometimes: reducing the risk of harming people —

Enjoy Testing

  The testers at work had a lean coffee session this week. One of the questions was  "I like testing best because ..." I said that I find the combination of technical, intellectual, and social challenges endlessly enjoyable, fascinating, and stimulating. That's easy to say, and it sounds good too, but today I wondered whether my work actually reflects it. So I made a list of some of the things I did in the last working week: investigating a production problem and pairing to file an incident report finding problems in the incident reporting process feeding back in various ways to various people about the reporting process facilitating a cross-team retrospective on the Kubernetes issue that affected my team's service participating in several lengthy calibration workshops as my team merges with another trying to walk a line between presenting my perspective on things I find important and over-contributing providing feedback and advice on the process identifying a

Testing is Knowledge Work

  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-- "We need some productivity metrics from testers" OK. I'd like to help you meet your need if I can but to do that I'll need to ask a few questions. Let's start with these: Who needs the metrics? Is there a particular pr

Risk-Based Testing Averse

  Joep Schuurkes started a thread on Twitter last week. What are the alternatives to risk-based testing? I listed a few activities that I thought we might agree were testing but not explicitly driven by a risk evaluation (with a light edit to take later discussion into account): Directed. Someone asks for something to be explored. Unthinking. Run the same scripted test cases we always do, regardless of the context. Sympathetic. Looking at something to understand it, before thinking about risks explicitly. In the thread , Stu Crook challenged these, suggesting that there must be some concern behind the activities. To Stu, the writing's on the wall for risk-based testing as a term because ... Everything is risk based, the question is, what risks are you going to optimise for? And I see this perspective but it reminds me that, as so often, there is a granularity tax in c

Agile Testing Questioned

Zenzi Ali has been running a book club on the Association for Software Testing Slack and over the last few weeks we've read Agile Testing Condensed by Janet Gregory and Lisa Crispin. Each chapter was taken as a jumping off point for one or two discussion points and I really enjoyed the opportunity to think about the questions Zenzi posed and sometimes pop a question or two back into the conversation as well. This post reproduces the questions and my answers, lightly edited for formatting. --00-- Ten principles of agile testing are given in the book. Do you think there is a foundational principle that the others must be built upon? In your experience, do you find that some of these principles are less or more important than others?  The text says they are for a team wanting to deliver the highest-quality product they can. If we can regard a motivation as a foundational principle, perhaps that could be it: each of the ten pr

The Great Post Office Scandal

  The Great Post Office Scandal by Nick Wallis is a depressing, dispiriting, and disheartening read. For anyone that cares about fairness and ethics in the relationship that business and technology has with individuals and wider society, at least. As a software tester working in the healthcare sector who has signed up to the ACM code of ethics through my membership of the Association for Software Testing I put myself firmly in that camp. Wallis does extraordinarily well to weave a compelling and readable narrative out of a years-long story with a large and constantly-changing cast and depth across subjects ranging from the intensely personal to extremely technical, and through procedure, jurisprudence, politics, and corporate governance. I won't try to summarise that story here (although Wikipedia takes a couple of stabs at it ) but I'll pull out a handful of threads that I think testers might be interested in: The unbelievable naivety which lead to Horizon (the system at th

Testing and Semantics

The other day I got tagged on a Twitter thread started by Wicked Witch of the Test about people with a background in linguistics who’ve ended up in testing. That prompted me to think about the language concepts I've found valuable in my day job, then I started listing them, and then realised how many of them I've mentioned here over the years .   This post is one of an occasional series collecting some of those thoughts.  --00-- In this series so far we've looked at words and syntax. In both cases we've found that natural language is an imprecise medium for communication. We might know the same words and grammar as others ... but they will have their own idea about what they mean ... and even where we agree there is ambguity ... and all of us, the world, and the language are evolving ... all the time. Today we'll add semantics which, in a pleasing twist, is itself ambiguo

Leaps and Boundary Objects

Brian Marick  recently launched a new podcast, Oddly Influenced . I said this about it on Twitter: Boundary Objects, the first episode of @marick's podcast, is thought-provoking and densely-packed with some lovely turns of phrase. I played it twice in a row. Very roughly, boundary objects are things or concepts that help different interest groups to collaborate by being ambiguous enough to be meaningful and motivational to all parties. Wikipedia  elaborates, somewhat formally:  [boundary objects are] both plastic enough to adapt to local needs and constraints of the several parties employing them, yet robust enough to maintain a common identity across sites ... The creation and management of boundary objects is key in developing and maintaining coherence across intersecting social worlds. The podcast talks about boundary objects in general and then applies the idea to software development specifically, casting acceptance test

Personal Development

The other day I got tagged on a Twitter conversation between a couple of my colleagues, Ben Dowen and Dan Ashby , which ended with Ben citing me as an example: But there is a trap, in that a Dev who Tests, or Tester who codes both risk becoming Test Automators ... The counter argument is Testers who code can do as @qahiccupps does, and use and build tools to explore. A jumble of thoughts tumbled out as I read it and here they are, in no particular order. It is flattering to be mentioned but I'm far from the only person doing this. Maaret Pyhäjärvi   and Rob Sabourin are vocal about the value it can bring and go out of their way to tell and teach others how to get it. Ben is right when he says I use coding as a tool, and as a tool factory. It's a means to an end. Coding itself doesn't give me a lot of pleasure. Having created a useful thing gives me an enormous amount of pleasure. I am not a great developer. But then I rarely need to be.   Yes, I have made bug fixes that