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?"

"Wine?"

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

"'Night."

"'Neiggghhht."

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.

"The Dev manager won the caption competition again."

Image: http://flic.kr/p/9dHgZ9

Comments

Unknown said…

Reminds me of slides 50 + 51 of the RST course (http://www.satisfice.com/rst.pdf)

August 28, 2013 at 1:38 PM

James Thomas said…

@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).

August 29, 2013 at 9:56 AM

Paul Gerrard said…

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

http://gerrardconsulting.com/?q=node/491

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)

September 2, 2013 at 12:23 PM

James Thomas said…

@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?

September 3, 2013 at 7:04 AM

Paul Gerrard said…

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

September 3, 2013 at 6:39 PM

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

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

The Best Programmer Dan Knows

I was pairing with my friend Vernon at work last week, on a tool I've been developing. He was smiling broadly as I talked him through what I'd done because we've been here before. The tool facilitates a task that's time-consuming, inefficient, error-prone, tiresome, and important to get right. Vern knows that those kinds of factors trigger me to change or build something, and that's why he was struggling not to laugh out loud. He held himself together and asked a bunch of sensible questions about the need, the desired outcome, and the approach I'd taken. Then he mentioned a talk by Daniel Terhorst-North, called The Best Programmer I Know, and said that much of it paralleled what he sees me doing. It was my turn to laugh then, because I am not a good programmer, and I thought he knew that already. What I do accept, though, is that I am focussed on the value that programs can give, and getting some of that value as early as possible. He sent me a link to the ta...

Beginning Sketchnoting

In September 2017 I attended Ian Johnson 's visual note-taking workshop at DDD East Anglia . For the rest of the day I made sketchnotes, including during Karo Stoltzenburg 's talk on exploratory testing for developers (sketch below), and since then I've been doing it on a regular basis. Karo recently asked whether I'd do a Team Eating (the Linguamatics brown bag lunch thing) on sketchnoting. I did, and this post captures some of what I said. Beginning sketchnoting, then. There's two sides to that: I still regard myself as a beginner at it, and today I'll give you some encouragement and some tips based on my experience, to begin sketchnoting for yourselves. I spend an enormous amount of time in situations where I find it helpful to take notes: testing, talking to colleagues about a problem, reading, 1-1 meetings, project meetings, workshops, conferences, and, and, and, and I could go on. I've long been interested in the approaches I've evol...

Not Strictly for the Birds

One of my chores takes me outside early in the morning and, if I time it right, I get to hear a charming chorus of birdsong from the trees in the gardens down our road, a relaxing layered soundscape of tuneful calls, chatter, and chirrupping. Interestingly, although I can tell from the number and variety of trills that there must be a large number of birds around, they are tricky to spot. I have found that by staring loosely at something, such as the silhouette of a tree's crown against the slowly brightening sky, I see more birds out of the corner of my eye than if I scan to look for them. The reason seems to be that my peripheral vision picks up movement against the wider background that direct inspection can miss. An optometrist I am not, but I do find myself staring at data a great deal, seeking relationships, patterns, or gaps. I idly wondered whether, if I filled my visual field with data, I might be able to exploit my peripheral vision in that quest. I have a wide monito...

ChatGPTesters

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-- "Why don’t we replace the testers with AI?" We have a good relationship so I feel safe telling you that my instinctive reaction, as a member of the T...

Vanilla Flavour Testing

I have been pairing with a new developer colleague recently. In our last session he asked me "is this normal testing?" saying that he'd never seen anything like it anywhere else that he'd worked. We finished the task we were on and then chatted about his question for a few minutes. This is a short summary of what I said. I would describe myself as context-driven . I don't take the same approach to testing every time, except in a meta way. I try to understand the important questions, who they are important to, and what the constraints on the work are. With that knowledge I look for productive, pragmatic, ways to explore whatever we're looking at to uncover valuable information or find a way to move on. I write test notes as I work in a format that I have found to be useful to me, colleagues, and stakeholders. For me, the notes should clearly state the mission and give a tl;dr summary of the findings and I like them to be public while I'm working not just w...

Build Quality

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 the build is green, the product is of sufficient quality to release" An interesting take, and one I wouldn't agree with in gener...

Postman Curlections

My team has been building a new service over the last few months. Until recently all the data it needs has been ingested at startup and our focus has been on the logic that processes the data, architecture, and infrastructure. This week we introduced a couple of new endpoints that enable the creation (through an HTTP POST) and update (PUT) of the fundamental data type (we call it a definition ) that the service operates on. I picked up the task of smoke testing the first implementations. I started out by asking the system under test to show me what it can do by using Postman to submit requests and inspecting the results. It was the kinds of things you'd imagine, including: submit some definitions (of various structure, size, intent, name, identifiers, etc) resubmit the same definitions (identical, sharing keys, with variations, etc) retrieve the submitted definitions (using whatever endpoints exist to show some view of them) compare definitions I submitted fro...

Express, Listen, and Field

Last weekend I participated in the LLandegfan Exploratory Workshop on Testing (LLEWT) 2024, a peer conference in a small parish hall on Anglesey, north Wales. The topic was communication and I shared my sketchnotes and a mind map from the day a few days ago. This post summarises my experience report. Express, Listen, and Field Just about the most hands-on, practical, and valuable training I have ever done was on assertiveness with a local Cambridge coach, Laura Dain . In it she introduced Express, Listen, and Field (ELF), distilled from her experience across many years in the women’s movement, business, and academia. ELF: say your key message clearly and calmly, actively listen to the response, and then focus only on what is relevant to your needs. I blogged a little about it back in 2017 and I've been using it ever since. Assertiveness In a previous role, I was the manager of a test team and organised training for the whole ...

Hiccupps

Search This Blog