Skip to main content

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--
&c
Image: Wikipedia

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

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

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

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

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

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

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 general. That surprises you? Well, ho

Make, Fix, and Test

A few weeks ago, in A Good Tester is All Over the Place , Joep Schuurkes described a model of testing work based on three axes: do testing yourself or support testing by others be embedded in a team or be part of a separate team do your job or improve the system It resonated with me and the other testers I shared it with at work, and it resurfaced in my mind while I was reflecting on some of the tasks I've picked up recently and what they have involved, at least in the way I've chosen to address them. Here's three examples: Documentation Generation We have an internal tool that generates documentation in Confluence by extracting and combining images and text from a handful of sources. Although useful, it ran very slowly or not at all so one of the developers performed major surgery on it. Up to that point, I had never taken much interest in the tool and I could have safely ignored this piece of work too because it would have been tested by

The Best Laid Test Plans

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-- "What's the best format for a test plan?" I'll side-step the conversation about what a test plan is and just say that the format you should use is one that works for you, your coll