Skip to main content

Testing is an Onion

The other day Michael Bolton tweeted this
"Art" is the activity of directing attention to things and providing affordances for interpretations. Which is why testing IS an art.
I love this tweet not least because it itself affords so much opportunity for interpretation. I'm intrigued by its possibilities. I found myself picking at it, perhaps even factoring it. A few thoughts ...

"Art" is quoted. Are these scare quotes? Do they suggest some uncertainty, disagreement or ironic intent? Or are they merely an alternative to some stylistic markup such as bold font that you might see in a dictionary definition?

"Is" is emphasised in the second sentence. On that verb, that kind of marker might signify a refutation of some other assertion. Could that be the case here? What else might it be contributing?

Both "art" and "an art" are used. The former is frequently defined in terms of beauty whereas the latter is usually applied to a task that requires skill (e.g. Oxford Dictionaries). It's possible for one thing to be both. Is the use of both deliberate? Is it significant?
Natural languages contain much exception and idiom and do not lend themselves to rules and conventions. Which is why testing IS a language.   
"Affordances" is a relatively uncommon and quite technical word. Wikipedia describes an affordance as "a quality of an object, or an environment, which allows an individual to perform an action" but points out several variant usages. Might it have been chosen because it is the only word that gives the precisely nuanced meaning that was desired? Or because its rarity provides memorability to the whole? Or something else? Whatever the reason, it's a sore thumb here and potentially brings more than its core meaning.

The first sentence might be a definition of the term "art". It might be metaphorical  or analogy. It might be explication. It might merely be attributing some property to the concept. Which is it? It is any? Could it be more than one?

The format of the tweet is syllogistic, probably a variant of the Fallacy of the Undistributed Middle  in which there's an implicit premise, "testing is the activity of directing attention to things and providing affordances for interpretations". If you interpret the text literally, then it is subject to a potential logical fallacy and the extent to which you accept it depends on the extent to which you believe that the set of all art encompasses the set of all testing.

Even if your interpretation is not literal the implicit premise is hard to avoid.

Semantics is the study of meaning. Compositional semantics builds the meaning of the whole from the meaning of the parts. For instance, you can work upwards from the meanings of words via the grammar of each sentence to the meaning of the entire tweet. Restrictions are placed on higher-level potential interpretations by concrete interpretations of the components.  But it's both a bane and a beauty of natural language that the information transmitted can be a gestalt: more than the sum of the words.
"Pragmatics" is the identification and application of context to observation. Which is why testing IS pragmatics.
Pragmatics is a layer of meaning above semantics where context is added to the interpretation.  With the right context, any and all aspects of meaning can be changed, however logical or illogical they may appear to be without it. Stylistic considerations and communicative intent can form part of this wider context. What kinds of contexts might wrap around this tweet? And need they be exclusive? A few more thoughts ...

Perhaps the structure of the tweet is simply a rhetorical device for attributing characteristics to testing. It doesn't do to overlook the obvious. Sometimes.

There's a tradition of discussion about whether testing is an art and/or a science, or art or science, or artistic or scientific. The tweet locates itself in that tradition by its subject matter.

But maybe it's also part of some specific chain of dialogue or discussion that we aren't seeing the rest of in the Twitter timeline. We've said the emphatic "is" could be a response to some other statement, something like this:
"Art" is an activity that is driven by aesthetics. Which is why testing is NOT an art.
Perhaps it is sarcastic, trying to illustrate the way that carefully chosen wording can associate two distinct concepts to justify some position.

Michael has a self-declared Mcluhanite tendency to say things for their provocative effect, to make others think. So perhaps I've fallen into his trap and I'm self-yanking my chain here.

Perhaps it's just a throwaway tweet and doesn't bear any inspection: it's not intended to have any meaning beyond recording a thought in the moment it was originated.

Language can be a noisy channel for communication and Twitter as a medium naturally emphasises this because of its limit on length. But in other places other constraints apply - time, budget, the expected reader, the skills of the writer and so on. In those places and at those times where we need to minimise noise and maximise signal the onus is on us to do so by considering the kinds of messages we're sending or receiving: the words themselves and the context in which they're bundled.
Onions are made up of layers which can be difficult to uncover individually without skill and effort (and they can make you cry). Which is why testing IS an onion.
P.S. Michael was kind enough to criticise an early draft of this post and my motivation for writing it. Somewhat ironically, but entirely correctly, he identified that both could be clearer.
Image: http://flic.kr/p/9EEfp1

Comments

  1. Its a good point, "Testing is an Onion, some times make the team cry :( ". :)

    ReplyDelete

Post a Comment

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 answer would be almost meaningless and certa

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

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

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

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 Tester's Union, is to ask why we don&

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

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

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

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

My Frame, Your Thing

I was talking with a colleague the other week and we got onto the topic of framing our work. This is one of my suggestions: I want to help whoever I'm working with build the best version of their thing, whatever 'best' means for them, given the constraints they have. That's it. Chef's kiss. I like it because it packs in, for example: exploration of ideas, software, process, business choices, and legal considerations conversations about budget, scope, resources, dreams, and priorities communicating findings, hypotheses, and suggestions helping to break down the work, organise the work, and facilitate the work making connections, pulling information from outside, and sharing information from inside It doesn't mean that I have no core expertise to bring, no scope for judgement, no agency, and no way to be creative or express myself, and it specifically does not mean that I'm going to pick up all the crap that no-one else wants to do.  Of course, I might pick up