Skip to main content

Have a Slice Day!

 

I demoed some of my testing to Maaret Pyhäjärvi the other day. She asked a bunch of incisive questions, offered some helpful ideas on framing my results, and then suggested that I should consider speaking and writing about how I partition the testing space when I work. 

She followed up on Mastodon

... I learn so much hearing how [James] dissects the exact necessary information and combines it with an approach that provides better results than what is usual for testing.

Which, naturally, made me blush, but also reminded me that others have observed similar things. Back in 2016, during my presentation at MEWT #5, Iain McCowatt tweeted this:

[James] wields distinctions like a surgeon wields a scalpel.

So now I am wondering about how I can begin to externalise more of this aspect of my approach to testing.

I don't have the answer yet. Today's task is to collect some data on what I've said in the past. I'm listing it in the order I found it, with some commentary.

I have written and spoken a lot about how I test already although I would guess it's largely in the context of specific projects. Off the top of my head, How To Test Anything is more generic than others but, interestingly it doesn't talk specifically about this topic.

However, a term that comes to mind immediately is factoring. I searched for a definition of it in software testing and came up with this post by Rikard Edgren which also uses the term fractionation after Edward de Bono in Lateral Thinking.

I have read Lateral Thinking and recall that I wrote some notes about it. Skimming them now, I see that I didn't pick fractionation out, but I did say this:

Over the years I've come to value up-front exploration ... to build a model of the problem space before implementation. Frequently, even where the budget for a project is tiny, I'll try to isolate some time, however small, for it.

That post also mentions humour and triggers the thought that I mentioned factoring in my first talk, Your Testing is a Joke. This is from the paper that went with the presentation:

... I will often pick out ... entities and then look for concepts ... related to them ... and then see whether any of those concepts could link to one another or something related. I call this expansion and it feels like a close cousin of factoring. But where factoring is a process which seeks to list the intrinsic dimensions of a thing that may be relevant to the task in hand, expansion additionally looks for more general properties, instances, sub-parts, synonyms, antonyms and other related terms.

I had forgotten that I called this expansion at one point.

As I move through this thread of thoughts and think that I might have something to say about it, The Dots popped into my head. It seems like, as so often, I have already said something about it.

Side note: one of the reasons that I find blogging valuable is that I can search and see what I think, or thought.

In this case, I still think idea strings are relevant to the topic at hand: an idea leads to an idea leads to an idea, or more than one idea. The challenge, as in testing, is to decide which thread to pull, and how far, and when.

In this case I didn't pursue that line further. I instead searched Hiccupps for other mentions of factoring and found a post I'd forgotten about, The Anatomy of a Definition of Testing. If you take a look at it, you can see that I've tried to group ideas together to understand the space I'm looking at and then chosen a piece of it to attack. That's an example of exactly the concept we're talking about.

Tracking back, that post comes from another, Testing All the Way Down, and Other Directions where I said:

I am testing the definition of testing in [Explore It!] using my testing skills to find and interpret evidence, skills such as: reading, re-reading, skim reading, searching, cataloguing, note-taking, cross-referencing, grouping related terms, looking for consistency and inconsistency within and outside the book, comparing to my own intuition, reflecting on the reaction of my colleagues ..., filtering, factoring, staying alert, experimenting, evaluating, scepticism, critical thinking, lateral thinking, ...

That may also be the first post where I talked about the non-linearity inherent in our work. We rarely discover all that we need to know at the time we need to know it in the order it makes most sense that allows us to get to some mythical right answer.

I'll stop there for now. It's nearly tea time and I feel like this is a good start. I have identified some points in the space I'm considering and some material I can review in more depth if I want it.

To be honest, I like to leave a task at this point and let my subconscious work on it for a while. What else do I already know here? What ways can I classify these things? How could I connect these ideas? How could I rearrange these things to make a contradiction?

I also like that I've captured something of the way I work here, so this post is itself an example of the thing I'm trying to think about. As I write that, a phrase arrives in my fingers: collect, arrange, slice. I don't know quite what I mean by it yet, but I'll keep it with the rest for now.
Image: https://flic.kr/p/owvFxg

Edit: I later wrote Collect, Arrange, and Slice

Comments

Popular posts from this blog

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

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

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

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

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

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

Not a Happy Place

  A few months ago I stopped having therapy because I felt I had stabilised myself enough to navigate life without it. For the time being, anyway.  I'm sure the counselling helped me but I couldn't tell you how and I've chosen not to look deeply into it. For someone who is usually pretty analytical this is perhaps an interesting decision but I knew that I didn't want to be second-guessing my counsellor, Sue, or mentally cross-referencing stuff that I'd researched while we were talking. And talk was what we mostly did, with Sue suggesting hardly any specific tools for me to try. One that she did recommend was finding a happy place to visualise, somewhere that I could be out of the moment for a moment to calm disruptive thoughts. (Something like this .) Surprisingly, I found that I couldn't conjure anywhere up inside my head. That's when I realised that I've always had difficulty seeing with my mind's eye but never called it out. If I try to imagine ev...

Why Question?

Questions are a powerful testing tool and, like any tool, can be used in different ways in different scenarios with different motivations and different results. A significant part of my role is generating questions and I will generally have a lot of them. I will rarely ask them all, though, and I've put a lot of time and effort into learning to be comfortable with that. A couple of examples: I was in a meeting this week where the technical conversation was too deep for me to give a perspective from a position of knowledge. I could have disengaged, but I didn't. Instead, I asked occasional questions, not wanting to derail the discussion or disrupt the flow. Some were detail questions, to help grow my understanding. Some were scoping questions, to help understand motivations. The one that really landed, however, was about the focus of the meeting. Although I couldn't contribute at a low level, I understood enough to suspect that we were not discussing the key problem tha...