Skip to main content

How to Test Anything


This post is a prettied-up version of the notes I made in advance of my talk, How To Test Anything, at the OnlineTestConf 2020 this week. Here's the abstract:

Sometimes you’re asked to start testing in a context that is not ideal: you’ve only just joined the project, the test environment is broken, the product is migrating to a new stack, the developer has left, no-one seems quite sure what’s being done or why, and there is not much time. 

Knowing where to begin and what to focus on can be difficult and so in this talk I’ll describe how I try to meet that challenge.

I’ll share a definition of testing which helps me to navigate uncertainty across contexts and decide on a starting point. I’ll catalogue tools that I use regularly such as conversation, modelling, and drawing; the rule of three, heuristics, and background knowledge; mission-setting, hypothesis generation, and comparison. I’ll show how they’ve helped me in my testing, and how I iterate over different approaches regularly to focus my testing.

The takeaways from this talk will be a distillation of hard-won, hands-on experience that has given me
    • an expansive, iterative view of testing
    • a comprehensive catalogue of testing tools
    • the confidence to start testing anything from anywhere
--00--

How to test anything, then. The title felt gooooood when I proposed it after being invited to speak at the conference, but not so much when I came to write the talk! 


I'm very much not an egotist and the message I want to convey here is not that you should test in the patented, certified, Thomas Way. Rather, I think that there are useful approaches to testing independent of the application and the context, and I want to share the ones that I use and how I use them.

Let's start with a thought experiment.


You are watching a robot and me — a tester —  interacting with the same system. Our actions are, to the extent that you can tell, identical and the system is in the same state at each point in the sequence of actions for both of us. The machine and me performed the same actions on the same system with the same visible outcomes.

If I told you I was testing, would you feel comfortable saying that the robot was testing too? I’d have a hard time saying that it was. Harry Collins and Martin Kusch, in The Shape of Actions, reckon that:

Automation of some task becomes tractable at the point where we become indifferent to the details of it.

I'm not bashing automation — I’m a regular user of automation as a tool in testing — but whatever complexity you put into your robot, my instinct is that it's not going to be as flexible as a human could be when encountering a given situation, particularly an unforeseen one.  Automation naturally can’t consider all the details, filtering out only the ones that seem interesting given knowledge of the context in the way that a human can.

For me, testing requires there to be intent, deliberate actions, agency, and responsiveness to observation on the part of the tester. I also have a strong idea of what is required for something to be tested.


In this post, I’ll describe what testing is for me, I’ll list some of the testing tools that I think are useful across contexts, and I'll give a simple heuristic for starting testing when you're stuck.


So what is testing? Arborosa has collected many definitions dating back to the 1950s and I spent some time a couple of years ago looking over them and reflecting on how I like to work, before coming up with a definition that works for me:

Testing is the pursuit of relevant incongruity

Boom! It’s a mouthful, but I can unpack it.

Incongruity: Oxford Dictionaries define this as "not in harmony or keeping with the surroundings". I interpret lack of harmony as a potential problem and lack of keeping as an actual problem, and those two interpretations are interesting and useful in testing.

Pursuit: Again, there are two senses that capture important aspects of testing for me. You can pursue something that you don't know is there and that you may never find, like a dream. Or you can pursue the solution to a problem that you know you have, that's right in front of you. 

Relevant: if this work doesn't matter to anyone, why are we doing it? Whoever that is can help us to understand whether any incongruities we identify are valuable to them, relevant to the project.

Which is great but, so what? Well, I can use it as a yardstick to gauge my activity against: I might want to be testing but realise I’m doing something else; I might be happy to do choose to do stuff that needs doing but isn’t testing.

Testing doesn't proceed in a linear fashion for me, either. I will typically choose to do something, get data from it, review that data, and then decide what to do next in a cycle.


To help me to test, I use tools. I've listed some of them here:


And what is a tool? For me it's simply a thing used to help perform a job and I've thought a lot about tools. (Take Your Pick: Part 1, Part 2, Part 3, Part 4.)

I have a toolbox that I carry with me, and I've taken care to become familiar with the tools so that I can reach for a tool that looks appropriate when I need it. My shed is organised the same way:


I like also to have a cache of stuff that isn't tools I'm familiar with and skilled at using, but which might come in handy, like this box of bits I've emptied out onto my bench. Sometimes the shape of the problem in front of you doesn't fit the shape of any of your tools, but there may be something in the box that can be offered up to it.


Perhaps I've used Selenium and have a grasp of its workings, its pros, and its cons. That's a tool and it's on my shelf. Let's say I've seen a webinar about Cypress and talked to a couple of team members who have experimented with it. That's in my box. If I see a problem that is similar to one I might use Selenium for, but isn't quite the right shape, I might reach for Cypress.

It's also important to practice with your tools. Learn when they apply well and when they don't. This tunes your intuition about when they'll be helpful or when they're actively working against your need. It also helps you to keep up to date and skilled with them. 

Here's a few of the tools I use all the time:
The best testers will be layering their activities. They’ll have a mission in mind but will be consciously trying to approach it in a way that gives them the chance to uncover other things. For example, they might be able to think of three ways to check some functionality and they’ll choose the one that exposes them to a bit of the product they haven’t seen much of, or has recently changed; maybe they’ll see a usability issue, or a performance problem that way.

The skilled tester might leave environments around when they’re finished with them so that some other later testing can be done in a dirty environment not in something that has been set up just for the test. Sometimes just coming back to a system that has been running by itself for a few days can show a problem.

I urge you to do this kind of conscious, intentful testing! Of course, a prerequisite for that  is starting and sometimes it's not easy.


Yes, it can be challenging because you don't want to make a mistake, to look foolish in front of new team mates, or set the project off down the wrong path. But I have a helpful heuristic:


You don’t necessarily need to wait for the requirements, or stability, or even a build of the application under test to start testing. Begin where you are!

Some factors that can help you to understand where you are:
  • constraints: budget, resources, time, ...
  • context: what is this product for, who is it for, what do they want to do, ...
  • value: who are your stakeholders, what are they looking for from you, ...
Choosing what to do next to deliver value to the project is setting your mission and I like to frame my missions using this slight variant of Elisabeth Hendrickson's charter template:


On a recent project I joined, I thought that the biggest challenge to customer and business value was (the way I saw it) disagreement amongst three stakeholders. In this case, I wrote a 2-page product description that crystallised what I thought we were building and importantly what I thought we were not building. When this was put in front of the team, and the stakeholders, we were able to have a conversation that squeezed out the differences.

You might reasonably ask whether I was testing. I think that in the main I was, yes. I was pursuing relevant incongruity.

I said three key things were needed for testing but in fact there's a fourth: something to test. I realised while I was writing the talk that I've encapsulated pretty much everything I've said so far in a page on my team's wiki. I pair with someone from my team every week. As a manager, ad hoc pairing is tricky for me to set up, but a recurring calendar appointment works. So I came up with some guidelines to help others help me to be involved:


I like to set the mission so that we are intentional and I like to reflect so that we have a chance to learn and change, but the key thing here is that I'm happy to start anywhere on anything completely from cold. I'm confident that I can bring something to the party wherever, whenever, and whatever that party is.  

So that's how I test anything: I have an idea what testing means for me, I find and practice with tools that help me to achieve it, and I'm not afraid to start from where I am and iterate.

Here's the video and full slides:


Comments

  1. Thank you James for your blog post, it was insightful. I am also to have found Elisabeth Hendrickson's charter template through your blog.

    ReplyDelete
    Replies
    1. Thanks, Trevor. I hope you find the template as useful as I have over the years.

      Delete

Post a Comment

Popular posts from this blog

Enjoy Testing

  The testers at work had a lean coffee session this week. One of the questions was  "I like testing best because ..." I said that I find the combination of technical, intellectual, and social challenges endlessly enjoyable, fascinating, and stimulating. That's easy to say, and it sounds good too, but today I wondered whether my work actually reflects it. So I made a list of some of the things I did in the last working week: investigating a production problem and pairing to file an incident report finding problems in the incident reporting process feeding back in various ways to various people about the reporting process facilitating a cross-team retrospective on the Kubernetes issue that affected my team's service participating in several lengthy calibration workshops as my team merges with another trying to walk a line between presenting my perspective on things I find important and over-contributing providing feedback and advice on the process identifying a

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

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

The Great Post Office Scandal

  The Great Post Office Scandal by Nick Wallis is a depressing, dispiriting, and disheartening read. For anyone that cares about fairness and ethics in the relationship that business and technology has with individuals and wider society, at least. As a software tester working in the healthcare sector who has signed up to the ACM code of ethics through my membership of the Association for Software Testing I put myself firmly in that camp. Wallis does extraordinarily well to weave a compelling and readable narrative out of a years-long story with a large and constantly-changing cast and depth across subjects ranging from the intensely personal to extremely technical, and through procedure, jurisprudence, politics, and corporate governance. I won't try to summarise that story here (although Wikipedia takes a couple of stabs at it ) but I'll pull out a handful of threads that I think testers might be interested in: The unbelievable naivety which lead to Horizon (the system at th

Agile Testing Questioned

Zenzi Ali has been running a book club on the Association for Software Testing Slack and over the last few weeks we've read Agile Testing Condensed by Janet Gregory and Lisa Crispin. Each chapter was taken as a jumping off point for one or two discussion points and I really enjoyed the opportunity to think about the questions Zenzi posed and sometimes pop a question or two back into the conversation as well. This post reproduces the questions and my answers, lightly edited for formatting. --00-- Ten principles of agile testing are given in the book. Do you think there is a foundational principle that the others must be built upon? In your experience, do you find that some of these principles are less or more important than others?  The text says they are for a team wanting to deliver the highest-quality product they can. If we can regard a motivation as a foundational principle, perhaps that could be it: each of the ten pr

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

Leaps and Boundary Objects

Brian Marick  recently launched a new podcast, Oddly Influenced . I said this about it on Twitter: Boundary Objects, the first episode of @marick's podcast, is thought-provoking and densely-packed with some lovely turns of phrase. I played it twice in a row. Very roughly, boundary objects are things or concepts that help different interest groups to collaborate by being ambiguous enough to be meaningful and motivational to all parties. Wikipedia  elaborates, somewhat formally:  [boundary objects are] both plastic enough to adapt to local needs and constraints of the several parties employing them, yet robust enough to maintain a common identity across sites ... The creation and management of boundary objects is key in developing and maintaining coherence across intersecting social worlds. The podcast talks about boundary objects in general and then applies the idea to software development specifically, casting acceptance test

Where No-one Else Looks

In yesterday's post, Optimising start of your exploratory testing , Maaret Pyhäjärvi lists anti-patterns she's observed in testers that can lead to shallow outcomes of testing. She ends with this call: Go find (some of) what the others have missed! That strikes a chord. In Toujours Testing I recalled how my young daughter, in her self-appointed role as a Thing Searcher, had asked me how she could find things that no-one else finds. I replied Look where no-one else looks. Which made her happy, but also made me happy because that instinctive response externalised something that had previously been internal.  The phrase has stuck, too, and I recall it when I'm working. It doesn't mean targeting the obscure, although it can mean that.  It also doesn't mean not looking at areas that have previously been covered, although again it can mean that. More, for me, it is about seeking levels of granularity, or perspectives, or methods of engagement, or personas, or data, or im

Am I Wrong?

I happened across Exploratory Testing: Why Is It Not Ideal for Agile Projects? by Vitaly Prus this week and I was triggered. But why? I took a few minutes to think that through. Partly, I guess, I feel directly challenged. I work on an agile project (by the definition in the article) and I would say that I use exclusively exploratory testing. Naturally, I like to think I'm doing a good job. Am I wrong? After calming down, and re-reading the article a couple of times, I don't think so. 😸 From the start, even the title makes me tense. The ideal solution is a perfect solution, the best solution. My context-driven instincts are reluctant to accept the premise, and I wonder what the author thinks is an ideal solution for an agile project, or any project. I notice also that I slid so easily from "an approach is not ideal" into "I am not doing a good job" and, in retrospect, that makes me smile. It doesn't do any harm to be reminded that your cognitive bias

External Brains

A month or two ago, after seeing how I was taking notes and sharing information, a colleague pointed me at Tiego Forte's blog on Building a Second Brain : [BASB is] a methodology for saving and systematically reminding us of the ideas, inspirations, insights, and connections we’ve gained through our experience. It expands our memory and our intellect... That definitely sounded like my kind of thing so I ordered the upcoming book, waited for it to arrive, and then read it in a couple of sittings. Very crudely, I'd summarise it something like this: notes are atomic items, each one a single idea, and are not just textual notes should capture what your gut tells you could be valuable notes should capture what you think you need right now notes should preserve important context for restarting work notes on a topic are bundled in a folder for a Project, Area, or Resource and moved into Archive when they're done. ( PARA )