See It! Days 1-5

This post is part of a series showing my working through the 2025 Advent of System Seeing exercises set by Ruth Malan. For background see the introduction.

The initial exercises introduce some core concepts and a couple of approaches to modelling, and encourage us to think about our work and the system we're looking at.

Day 1

Task: (1) Draw a Bubble Diagram of a bicycle (2) Sketch a bicycle from memory (3) Pick a key capability [and use] sketches and words to explore and convey how it works (4) Reflect on what you learned.

I'm comfortable doing what I'd call "factoring" which tries to find different angles or features or affordances of a thing that could be useful seams to follow when testing. I've used plenty of tools, such as the Six Thinking Hats or SFDIPOT to help with that, and represented the outcomes with a mindmap often.

Although my in-the-moment reflection says that I didn't find the bubble diagram helpful, I can see now that it's because I didn't sacrifice any of my 15-20 minutes to reading the (long) reference. Having looked a little closer, I see that it's a tool used in architecture and the spatial aspects (proximity and size) attempt to model features of the physical design, making it more like a map than a traditional mindmap, where the diagram's topography is typically not part of the model it holds.

It makes me think of the building blocks of models and the hybrid models I've made (e.g. Going Underground, The Testing Kraftwerk, or Granularity Familiarity) and I think it'll be a useful tool to have in my back pocket in future.

Day 2

Task: Draw a diagram to explore the world around bicycles. Zoom out, so that "bicycle" is just one bubble in the centre of the diagram.

Where are the edges of the context? is a question I have asked myself many times. It's fascinating to see how other participants broke the space around the bike down, seeing concepts that I didn't and leaving out things that I did. Sebastian Hans suggested something important: "some contexts have more depth than others, maybe because I have more experience riding a bike than building one."

That's the thing: our biases are hugely influential in this kind of exercise and it takes conscious effort to leave them at the door. Having multiple people on a task can help either synchronously or by sharing the model with others for comment. Be careful though: I have seen conversations break down because two people have formed mental models that don't fit together. Externalising the models can help massively but I find many people reluctant to do it.

Day 3

Task: Use a Futures Wheel to explore a change that is impacting cycling or the bicycle industry, in terms of direct and indirect effects.

Another new diagram format for me, the Futures Wheel. Again I didn't spend any of my time reading about it in advance but this time the exercise contained enough clues to get me going. There's a flavour of of Weinberg's diagram of effects or causal loop diagrams but I like how this visualises things like ripples in a pond, moving outwards from a centre.

One of the challenges in designing anything that will exist in the world is anticipating the impacts, particularly given that the world is a complex system and the impacts are indirect and subject to feedback mechanisms. I like this diagram as a potential tool for exposing some of that visually.

Reviewing the other participants' work I was struck by how easy it is to fall into the trap of not describing the impact. I've done it myself here: "more accidents" (an impact) and "policing costs" (not an impact, as stated, but an area that will be impacted). I see this all the time when we do exercises such as risk storming at work. Describing the impact means being explicit about the mechanism, it's another deeper layer of analysis.

Day 4

Task: Draw a Rich Picture, exploring all that happens "behind the scenes" when you fill a kettle or pot with water.

Patrick Prill said everything I'd want to say about this one but I'd add links to Fail Here or Fail There, Read it and Weep, Fail Over.

Day 5

Task: Gather some of the thoughts that have been percolating around systems as the introductory page to a zine on 5x3 index cards.

In contrast to the other exercises so far, I took a few minutes to think about how I wanted to lay out a 5"x3" card. I quickly decided that the key thing I want to get across about systems is that it's easy to forget that you're looking at one.

I drew the hard-to-read central panel to try to make that point and then tried to list things that are relevant to getting a model of a system on either side. I didn't intend to categorise them as "to consider" and "to look for" before I started. I am still not sure they are good labels, but I kind of feel that the list on the left are things that could perhaps be considered in the abstract and on the right things that require looking at the system.

Very roughly.
Image: Inspired by Explore It! by Elisabeth Hendrickson. Pragmatic Press

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

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

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

Reasonable Doubt

In Your job is to deliver code you have proven to work Simon Willison writes: As software engineers we ... need to deliver code that works — and we need to include proof that it works as well. He is coming at this from the perspective of LLM-assisted coding, but most of what he says applies in general. I think this is a reasonable consise summary of his requirements for developers: Manual happy paths: get the system into an initial state, exercise the code, check that it has the desired effect on the state. Manual edge cases: no advice given, just a note that skill here is a sign of a senior engineer. Automated tests: should demonstrate the change like Manual happy paths but also fail if the change is reverted. He notes that, even though LLM tooling can write automated tests, it's humans who are accountable for the code and it's on us to "include evidence that it works as it should." Coincidentally, just the week before I read his post I told one of my...

Great Shot, Kid

This week I've been playing with altwalker , a model-based testing tool. To get the hang of it, I attempted to build a very simple model of a workflow that is supported by the service my team owns. Hacking away at the example code, and looking frequently at the docs, I was able to get up and running in a few hours, creating: a basic model: nodes for system states, edges for operations simple assertions: mainly consistency checks on the states client: HTTP client to implement the operations against the service's API I configured this so that altwalker will perform a random walk of the model, starting state data is randomised, and the client will choose randomly whenever offered an option. Why so much randomness? Because it means that, over successive runs, more of the infinite space of possible workflow executions will be covered. Once I had that basically working I wrote a shell script that would run this loop a number of times: call altwalker ...

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

LLEWT 2024

This weekend I was at LLEWT 2024, a peer conference on Anglesey , north Wales, discussing communication. Given the day jobs of the participants, it was no surprise that the experience reports and the conversations that followed them mostly focussed on software development contexts. Notes from my presentation are in Express, Listen, and Field . I made sketchnotes (below) for each presentation and a mindmap (above) to try to summarise the whole. Without much reflection yet, I guess I would pull these common high-level threads from the day: There are multiple reasons that communication fails ... like, duh! ... but having multiple strategies for framing a message can help ... and having multiple tactics for delivering a message can help too. Understanding what you want from an interaction is key ... so setting the context to make that more likely is wise ... which might mean meta-conversation, being transparent, or changing your approach...

PR Coup!

My team uses Dependabot to keep software dependencies up to date. The tool submits PRs against our repositories and we use a checklist/decision tree to help us judge how deeply to review and provide an audit trail of the decision. Patch-level updates of company-internal packages might be just waved in if the tests pass, for example, but a major update of an external library could require us to review or redo a risk analysis. For reasons , the Markdown source for the tree is not automatically added to the PR so we pick it up from another repo, copy it, and paste it into the PR we're looking at. This has got sufficiently irritating to me that I looked for another way. I know about bookmarklets and I've made them before, so I first tried to make one that would paste the text into a comment box on the PR. The checklist is long and I needed to escape various characters and retain line breaks and it was tricky to edit and debug in a simple URL field, so I aborted. I wondered if the...

The Love of a List and a Loop

I attended Maaret Pyhäjärvi 's Intro to Contemporary Exploratory Testing webinar for Codementor this week. In it, she demonstrated exploration with automation on Alan Richardson 's E-Prime checker web site using Playwright to provide control and visibility of the page and PyUnit to make assertions about its state. Nothing unusual there, you might say. There are probably millions of test suites with a similar setup running right now in companies all over the world. And you're right. What's different about this approach is what Maaret did with the tooling, and why. She created a simple skeleton test case, parameterised it to take an input and expected output, and interactively called it with test cases from a list. What she had now was a lightweight testing rig where: Adding a new test idea is adding a new item to the list. A note, bug report, or to-do is a comment above an item in the list. Variant ideas can be created quickly and easily with copy-p...

Exploring It!

This week the test team at Linguamatics held our first internal conference. There was no topic, but three broad categories could be seen in the talks and workshops that were given: experience reports, tooling, and alternative perspectives on our work. (The latter included the life cycle of a bug, and psychology in testing.) My contribution was an experience report looking at how I explore both inside and outside of testing. I've tidied up some of my notes from the prep for it below. There are testing skills that I use elsewhere in my life. Or perhaps there are skills from my life that I bring to testing. Maybe I'm so far down life's road that it's hard to tell quite what started where? Maybe I'm naturally this way and becoming a tester with an interest in improvement amped things up? Maybe I've so tangled up my work, life, and hobby that deciding where one starts and another ends is problematic? The answers to those questions is, I think, almost certai...

Hiccupps

Search This Blog