Skip to main content

In the Context of Context-Driven

I started an enjoyable discussion on Twitter the other day. Here's a brief summary.

So I idly wondered whether it was possible to construct a barber-style paradox around context-driven testing (CDT) and tweeted this:
A Context-Driven tester says that CDT is not applicable on some project, given the context, and tests accordingly. Is this CDT?
I deliberately left this ambiguous. It could mean a few things, including:
  • deciding how to test in the context
  • any testing activities undertaken after evaluation of context 
  • both of the above 
  • all of the work the tester does on that project
I think it's possible to make a case for all of them being CDT based on the original tweet. But it doesn't mean that any particular instance of them must be.

For example, the context-driven tester might not act in a context-driven way at some point (perhaps only context-aware). Or while not doing CDT the context-driven tester might actually be constantly re-evaluating the context looking for a point at which the context changes sufficiently to prefer another approach, i.e. practising CDT. The Twitter thread didn't really explore this aspect.

There was keen discussion about whether it was even possible to find a place that CDT was not appropriate and @huibschoots dug up a link to a Bach/Bolton presentation that suggests a few.

Some testers said that they would always do CDT here. This example from @kengel100:
@qahiccupps @huibschoots @kinofrost if I place myself in this situation there is still a need for CDT. Tester dependent?
In an attempt at clarity, multiple definitions of CDT are given at context-driven-testing.com. One includes this:
The essence of context-driven testing is project-appropriate application of skill and judgment.  
I didn't give any project context. There is none, it's a thought experiment. The context-driven-testing.com web site also says:
Context-driven testers reject the notion of best practices, because they present certain practices as appropriate independent of context. 
So I speculated about whether there was an argument that it is not context-driven to insist on CDT, particularly given that there are some occasions where it's plausible to think that CDT might legitimately not be used. I suppose I'm also thinking about whether asserting that you will always practice context-driven testing effectively makes CDT your best practice.
@kengel100 @huibschoots @kinofrost Interesting variant question. Is it CDT to say that we must approach any problem using CDT? Does a tester self-declared as CD use CDT in all contexts? (i.e. regardless of context)
@kinofrost put his response to the idea that there was a contradiction in having the intention to do CDT irrespective of context nicely:
@qahiccupps @kengel100 @huibschoots It's self-refuting. Like saying there's a car driver who always drives car irrespective of having a car.
So I ended up asking myself whether I was worrying away at a potential something or making a something out of nothing.
@kinofrost @kengel100 @huibschoots Started with a hypothetical corner. Wondering if I'm digging a hypothetical hole. 
Image: https://flic.kr/p/hnimz3

Comments

  1. There is a song by Love & Rockets--the first concert I ever went to that says, "You can not go against nature, because when you do, go against nature that's part of nature to. Our little lives get complicated. It's a simple thing. As simple as a flower, and that's a complicated thing."

    So, just like very long discussions about words, I don't see how this has anything to do with testing.

    ReplyDelete
  2. @TestyRedhead.

    I like that you've quoted a lyric because I had one in my mind when I was thinking about this too: "Everything in moderation, including moderation." I first heard it in a song by a long-since-gone band called Jumbo but it's attributed to Oscar Wilde here.

    I guess I disagree that there's no relation to testing here. If nothing else, questioning, probing definitions, challenging established concepts is part of what testing's about.

    I'll chalk one up to the "making a something out of nothing" score on your behalf.

    Cheers.

    ReplyDelete
  3. I love a bit of phylosophy in the morning. (Or any time). Like the 'I think therefore I am!'. But dpes that mean a thought truely has a life of it's own; can you be and not think, (I've met a few managers and project leads that seem to show you can be and not think) it can really mess with your head if you over think something like that.

    I would say that the statement that CDT doesn't like Best Practices is to general. You can make a best practice high enough level to still be flexible to cover all/most contexts. But in the end all testing has a context. Even if that context is limited to a set of requriements, or design specs. In the context of the designers intention we design tests to verify every button that they want. I realise this is probably not in the context of context driven testing, but context is just another word for perspective. And perspective, as with context, changes with each individual, each time of day, each location and agenda, and more variables.

    I would vote for 'something out of nothing'. But all in all a good thought exercise

    ReplyDelete

Post a Comment

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