Skip to main content

CEWT 3



CEWT is the Cambridge Exploratory Workshop on Testing, a peer discussion event on ideas in and around software testing. The third CEWT, held a week or so ago, had the topic Why do we Test, and What is Testing Anyway?  With six speakers and 12 participants in total, there was scope for a variety of viewpoints and perspectives to be voiced - and we heard them - but I'll pull out just three particular themes in my reflection on the event.

Who

Lee Hawkins viewed testing through the eyes of different players in the wider software development industry, and suggested aspects of what testing could be to them. For tools vendors or commercial conference organisers, testing is an activity from which money can be made; for financial officers, testing is an expense, something to be balanced against its return and other costs; for some managers and developers and even testers, testing is something to be automated and forgotten.

James Coombes also considered a range of actors, but he was reporting on how each of them - at his work - contribute to an overall testing effort: the developer, tester, security expert, technical author, support operator, integration tester, manager and customer. Each person's primary contribution in this approach is their expertise, their domain knowledge, their different emphasis, their different lenses through which to view the product.

In discussion, we noted that the co-ordination of this kind of activity is non-trivial and, to some extent, unofficial and outside of standard process. Personal relationships and the particular individuals concerned can easily make or break it.

There was also some debate about whether customers are testing a product when they use it. It's certainly the case that they may find issues, but should we regard testing as inherent in "normal use"? Does testing require intent on the part of the "tester"?

Why

Karo Stoltzenburg focussed on an individual tester's reasons for testing and concluded that she tests because it makes her happy. Her talk was a description of the kinds of testing she'd done, of herself, to arrive at this understanding and then to try to see whether her own experience can be generalised, and to who. She suggested that we, as testers, sell our craft short and called on us to tell others what a great job it is!

One particularly motivating slide gave a selection of responses from her work colleagues to the question "why do you test?", which included: it's like a puzzle, variety of challenges, a proper outlet for my inner pedant, it's fun. Lee's talk also included a set of people who found testing fun and he characterised them as people like us, people who love the craft of software testing.

Later, in his blog post about this event, Lee described the CEWT participants as "a passionate group of testers". There was an interesting conversation thread in which we asked why we were there, doing what we were doing, and what we'd do with whatever we got from it.

Why? is a powerful question. On a personal level, I enjoy talking about testing, about its practical aspects and in the abstract. I like being exposed to ideas from other practitioners (which is not to say that I get ideas only from other practitioners) and I like to get other perspectives on my own ideas.

And, of course, understanding our own motivations is interesting, but I think the conversations in the event rarely got very deeply into the motivations of other stakeholders who ask for, or just expect, testing. We did discuss questions such as "if the testing is being done by others, why do we need testers?" and again wondered whether what others were doing was testing, or contributing to testing, or both. Harry Collins' The Shape of Actions has things to say about the way in which activities can be broken down and viewed differently at different resolutions.

But to return to Karo's challenge to us: does an event like CEWT essentially have the choir singing to itself? We know why we like testing and we know that we implicitly value testing, because we do it and because we gave up a Sunday to talk about it. But we're self-selecting. The event can help us to support each other and improve ourselves and the work we do, but can it change other's views of testing? Should it? Why?

What

Michael Ambrose described a project concerned with increasing the software development skills of his test team. The aim was to write code in order to reduce the manual effort required to support testing of a wide range of platforms without reducing the coverage (in terms of the platform set).

Naturally, this begs questions such as: is the new software doing testing? is it replacing testing (and if so to what extent?) or augmenting testing? is it extending testing scope (e.g. by freeing testers to take on work that currently isn't being done at all)? what dimensions of coverage might be increased, reduced? how can its success be evaluated?

We talked a little during the day about the tacit testing that goes on outside of that which was planned or expected or intended by a tester: those things that a human will spot "in passing" that an algorithm would not even consider.

Does that tacit investigation fit into the testing/checking distinction? If so, it's surely in testing. But, again, how important is intent in testing activity? Is it sufficient to set out with the intent to test, and then anything done during that activity is testing?  What kind of stuff that happens in a tester's day might not be regarded as testing? One participant gave an example of projects on which 85% of effort was spent covering their arse.

In his talk, Aleksandar Simic presented a diary of two days in his role as a tester, and categorised what he did in various ways. These categorisations intriguingly included "obsession" which described how he didn't want to let an issue go, and how he spent his own time building background knowledge to help him at work. He talked about how he is keeping a daily diary of work done and his feelings about that work, and looking for patterns across them to help him to improve himself.

This is challenging. It's easy to mislead and be misled by ourselves. Seeing through our own rose-tinted spectacles involves being prepared to accept that they exist and need to be at least cleaned if not removed.

But is that kind of sense-making, data gathering and analysis a testing activity? I would like to regard it as such. In my own talk I explained how I had explored a definition of testing from Explore It! and also explored my reaction to it, and how these processes - and others - ran in parallel, and overlapped with, and impacted on each other. I rejected testing as simply linear and tried to find my own definition that encompasses the gloriously messy activity that it can be (for me).

One comment on my definition - which inverted a concern that I have about it - was that it is sufficiently open that people could buy into it, and read into it, particularly non-testers. This touches again on the topic of taking testing out of the testing bubble.

There was some thought that distinctions like testing vs checking - which have not been universally approved of in the wider testing community; some thinking that it is simply navel-gazing and semantics - are useful as a tool for conversations with non-testers. An example might be explaining why a unit test suite, valuable as it might be, need not be all that testing is.

Perhaps that's a useful finding for us: that we can get value from events like these by going away and being open to talking about testing, explaining it, justifying it, in ways that other parties can engage with. By doing that we might (a) spread the word about testing,  (b) understand what others want and need from it, and (c) have fun.

I am intellectually buoyed by events like this, and also not a little proud to see something I created providing a forum for, and returning pleasure and value to, others. CEWT 4 anyone?

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