The Warlock of Testing Mountain

Commiserating once again with a colleague about the frustrations of testing a complex (computer) system within a complex (human) system I said that it reminded me of the Fighting Fantasy books I used to play as a boy. In them, non-linear storylines are generated by choosing, or rolling dice to determine, how the story proceeds. Characters are typically engaged in some kind of quest, such as collecting gems, and have some attributes, such as strength, which are affected by interactions during the game.

As a little bit of amusement for myself I tweeted a few words that reflected something of the situation I found myself in at that moment. Then now and again over the next couple of weeks I extended it (fictitiously!) as if I was playing out a book. I've compiled the whole thread here.

62. You upgrade and rerun the test. Presently your client is wedged. Server logs have stopped and 'df -h' shows disk at 100%. You can start another lengthy and frustrating diagnosis (turn to 239) or kick a handy inanimate object repeatedly (turn to 18).

--00--

18. After a couple of taps, you let rip. The bin's parabolic arc pleases your eye, until you project its future trajectory onto a developer's head. Do you chase the bin (turn to 431), shout a warning (turn to 20) or quickly sit down (turn to 775).

--00--

775. You sit. It hits. Roll a dice. If the number is even the developer notices your guilty face and gives you the evil eye. (Turn to 43.) If odd, she looks past you at the tester whose bug reports she's been rejecting INVALID PROVIDE REPRO all week. (Turn to 7.)

--00--

7. You silently thank the Exploratory Gods, swearing again that you really will use Elisabeth Hendrickson's template, and have some sessions not putting naughty strings into text boxes. New session (turn to 322) or report to test lead (turn to 12).

--00--

12. The test lead looks up from Excel with heavy eyes as you approach. Do you throw a cheery wave and carry on past to the drinks machine, assuming now is not a good time (turn to 13) or pull up a chair, smile broadly, and ask to debrief (turn to 564).

--00--

13. At the drinks machine you spy a PO moaning about how the initial estimates justified his aggressive deadlines and sales forecasts. Throw a cheery wave and divert to the stationery cupboard (turn to 14) or die a little inside (turn to 643).

--00--

14. You collect several coloured pens, some post-its, and a novelty rubber from a recruitment agency with the slogan "Did the boss refuse your request for erase?"

Die a little inside (turn to 643), or new session (turn to 322).

--00--

322. You sit down heavily, bumping your desk and disturbing a large pile of unused pens and post-it notes which landslides onto your keyboard. Do you:

Brush it aside and start this session. Turn to 323.
Spend a couple of hours tidying. Turn to 236.

--00--

323. You unlock the computer. Your test system has broken. Roll two dice. If the sum is:

2. Test logging filled the disk.
3. Automatic update.
4. Network outage.
5-12. WTF??!!?

In all cases subtract 1 from AUTONOMY, MASTERY and PURPOSE. Turn to 324.

--00--

324. You run an Ansible playbook to reset the test environment. It fails. You sigh and open (yes!) Emacs.

Keep rolling a dice until you get the same score twice in a row. Add that score to MASTERY. On every roll, subtract 1 from PURPOSE.

Turn to 325.

--00--

325. You write "Mission:" on a new page in your notebook. PING! PING! two different right-now meeting alerts from the PO arrive. He clearly wants something. Do you:

Ignore. (Turn to 473.)
Reject, (Turn to 475.)
Sigh and go. (Turn to 477.)

--00--

473. "Mission" you say, "mmm mission: explore the thingy with the, erm, for, um, to prove, err to, what was it again?"

You search "Hendrickson Template" and an hour later your family Christmas card design is sorted… Turn to 474.

--00--

474. Eventually your environment is stable, your mission is set down, you have a fresh cuppa and you can begin testing.

Dive in. Turn to 112.
Make a test ideas mind map. Turn to 113.
Review specs. Turn to 114.
Ask the developer. Turn to 115.

--00--

112. You are going to test the fricken hell out of this. YEAH!

You start the app and click all buttons. No errors. Erm, done?

Cuppa! Then ...

Make a test ideas mind map. Turn to 113.
Review specs. Turn to 114.
Ask the developer. Turn to 115.

--00--

113. You draw a circle, write Tests in it, then space S, F, D, P, O, and T equally around it. You Google SFDPOT and, again, find I got added. You've no space for I.

Dive in. Turn to 112.
Review specs. Turn to 114.
Ask the developer. Turn to 115.

--00--

114. The spec is from 2013. It assumes a product you never built. You find this out only after spending three weeks on a test matrix. The author left in 2014.

Dive in. Turn to 112.
Make a test ideas mind map. Turn to 113.
Ask the developer. Turn to 115.

--00--

115. The developer glances at you, points at the expensive bluetooth headphones clamped to their ears, and turns back to their favourite subreddit.

Dive in. Turn to 112.
Make a test ideas mind map. Turn to 113.
Review specs. Turn to 114.

--00--

Image: Wikipedia

Comments

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

How do I Test AI?

Recently a few people have asked me how I test AI. I'm happy to share my experiences, but I frame the question more broadly, perhaps something like this: what kinds of things do I consider when testing systems with artificial intelligence components . I freestyled liberally the first time I answered but when the question came up again I thought I'd write a few bullets to help me remember key things. This post is the latest iteration of that list. Caveats: I'm not an expert; what you see below is a reminder of things to pick up on during conversations so it's quite minimal; it's also messy; it's absolutely not a guide or a set of best practices; each point should be applied in context; the categories are very rough; it's certainly not complete. Also note that I work with teams who really know what they're doing on the domain, tech, and medical safety fronts and some of the things listed here are things they'd typically do some or all of. Testing ...

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

Don't Know? Find Out!

In What We Know We Don't Know , Hillel Wayne crisply summarises a handful of research findings about software development, describes how the research is carried out and reviewed and how he explores it, and contrasts those evidence-based results with the pronouncements of charismatic thought leaders. He also notes how and why this kind of research is hard in the software world. I won't pull much from the talk because I want to encourage you to watch it. Go on, it's reasonably short, it's comprehensible for me at 1.25x, and you can skip the section on Domain-Driven Design (the talk was at DDD Europe) if that's not your bag. Let me just give the same example that he opens with: research shows that most code reviews focus more on the first file presented to reviewers rather than the most important file in the eye of the developer. What we should learn: flag the starting and other critical files to receive more productive reviews. You never even thought about that possi...

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

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

Software Sisyphus

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-- "How can I possibly test 'all the stuff' every iteration?" Whoa! There's a lot to unpack there, so let me break it down a little: who is suggesting that "al...

Hiccupps

Search This Blog