The Tester Connector

Connections. We spend our time searching for them, stumbling across them, postulating them, making them, questioning them, confirming them, creating them and breaking them. They might be between products, between bits of your product, between people, between the ideas different people have, between different ideas that you have, between what you've seen, what you're seeing and what you might hope or fear seeing next.

finding associations (or the lack of them) between the system under test and something else.
connecting the product's behaviour with some notion of what it's supposed to do - or not do.
building links between components in your mental model of how an application works.
relating a new bug to previous ones.
identifying areas of consensus or disagreement, bringing concepts and people together.

I think therefore I am is fine and dandy, M. Descartes, but for testers I wonder if this would be better: If I am not connecting, I am not.

I am. Or, at least, I was when I first thought it and asked myself whether it had any validity. And I guess I'm hoping to connect with you, right now. So let's say I am. Here's what happened...

While I was writing No F in Spec a couple of weeks ago I was also finishing up a round of annual appraisals and had recently attended a UK Test Management Forum meeting where I'd been introduced to the term futurespective. It occurred to me that there's a link between specification, introspection (which I'd been praising and encouraging in appraisal) and futurespective.

Coincidence to have them all drop on me at once but it piqued my interest and so I looked them up to see if they shared a common root. It turns that they're from two distinct Latin words (to view, to be specific) so there's no etymological connection, although it doesn't matter: it spurred an interesting thought, one that I'd never brought out explicitly before; specification as a view of (some aspects of) intended behaviour.

But the process of looking for the connection triggered another thought on the nature of connections themselves. I stored it away for later and wasn't actively pursuing it when the phase only connect floated into my mind. A phrase that I'd heard but never understood the context of. So I looked it up. Interesting. Later the same day I was browsing Twitter and this tweet from @kinofrost leapt out of my timeline:

Listening to @GaryDelaney on @ComComPod. Loads of information on cross-role and cross-purpose heuristics, totally fascinating.

Cross-role, cross-purpose? Connections! Delaney is a comedian whose stock in trade is the one-liner and in the podcast the tweet refers to he deconstructs one, explaining how he starts with a punchline and then looks for related ideas that can be used to build to it, enabling it to be seen only at the reveal. The humour comes from multiple connections being possible at the same time and the listener being forced to switch from one to the other. (In passing he also makes his own connections between the delivery style of comedians and evangelical preachers, hype men, Martin Luther King and Hitler.)

And in turn that reminded me of a forum post I made at the Software Testing Club a couple of years ago where I was asking what testers just do naturally that they think is useful to them as a testing tool. For me, punning is an innate habit and feels intuitively very similar to what Delaney describes: take some concept and run through things that have some kind of relationship to it looking for an ambiguity to exploit. James Christie noted that he, as a matter of course, "mentally check[s] relationships. Mistakes in newspapers leap out at me, like someone being born in 1940, then a few paragraphs later entering college at the age of 18 in 1957."

We both picked out habits that build relationships. I wondered whether the vogue for mind maps in testing is a reflection of this more generally? I began to see an analogy between a network of connections and an exploratory search space - which branch to follow? Why? When? I started to think about the value of being exposed to a wide range of inputs in order to enable more connections. I thought about the need to filter connections out to avoid noise; about how repeated bad connections - biases? - can be identified and cast aside. I speculated about testing heuristics and mnemonics as devices that suggest ways in which connections have been made previously in software testing and which could be useful again. And I thought more about how lateral thinking can be valuable in this respect too; with puns there's no reason for a logical relationship between two concepts to exist as long as the result is a useful one.

And so I started writing it up, to get it straight in my head - which is how it works best for me - and, in the course of doing that I realised I'm connecting with my earlier train of thought but wondering something more general this time: maybe testing isn't helped by the skill of making connections but instead maybe testing is making connections?

Then as I concluded that round of writing I found I'd connected back to the word archaeology I was doing at the beginning, with a new word I learned looking up my Latin. I'd ended up with an F in conspectus.
Image: "Novus planiglobii terrestris per utrumque polum conspectus" by http://maps.bpl.org, https://flic.kr/p/gFEjLk

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

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

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

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