In response to “context-driven testing” is the “don’t do stupid stuff” school of testing

I blogged about the Twitter conversation that ensued from this tweet from Katrina Clokie:

One of the threads that came out of this conversation narrowed the focus down to “schools of testing” and, in particular, the context-driven testing community:

There’s a bit to unpack here, so let me address these replies piece by piece.

“Divisive rhetoric from some of the thought leaders in that camp”

I can only assume that Rex was referring to the more vocal members of the CDT community, such as James Bach. I haven’t personally experienced anyone trying to be deliberately divisive in the CDT community, but I acknowledge that passion sometimes manifests itself in some strongly-worded comments. Even then, I wouldn’t see this as “rhetoric” as that implies a lack of sincerity or meaningful content. The CDT community, in my experience, attracts those who are sincere about improving software testing, the way it’s done, and the value it delivers.

The use of the term “thought leaders” is also interesting as I don’t see anyone within this community referring to themselves or anyone else as thought leaders. There are obviously more prominent members of the CDT community but also many doing great work in advancing the craft of software testing in line with the principles of CDT behind the scenes (i.e. not so vocally via avenues such as social media).

“CDT is more accurately called the “pay attention” or the “don’t do stupid stuff” school of testing”

I’m not sure whether Matt Griscom’s response was designed to provoke CDT community members or stemmed from a genuine misunderstanding of the seven principles of CDT, which are:

  1. The value of any practice depends on its context.
  2. There are good practices in context, but there are no best practices.
  3. People, working together, are the most important part of any project’s context.
  4. Projects unfold over time in ways that are often not predictable.
  5. The product is a solution. If the problem isn’t solved, the product doesn’t work.
  6. Good software testing is a challenging intellectual process.
  7. Only through judgment and skill, exercised cooperatively throughout the entire project, are we able to do the right things at the right times to effectively test our products.

I agree that we should all be paying attention as testers (or as any other contributor to a project). Paying attention to the broader project context is really important if we are to do a great job of testing, but it is still overlooked and too many testers seem to think the software in front of them is the most important (or, worse, only) aspect of the context that they need to care about.

The seven principles of CDT may well also help to decrease the chances of testers spending their time doing “stupid stuff”, but that seems like a good thing to me. Working in alignment with these principles is, to me, a better approach than following standards or “best practices” that fail to account for the unique context of the project I’m working in. I’d argue that many best practices or recommendations from other “schools” actively promote what would in fact be “stupid stuff” in many contexts.

“the value of the phrase “context-driven””

I don’t see “context-driven” as a phrase – we have a clear statement of the seven principles backing what “context-driven testing” is (see above) and the value comes from understanding what those principles mean and performing testing in alignment with them. Rex replied on Matt’s request for enlightenment, saying “”Marketing” is the value enjoyed by a small few testers. “Schism” is the price paid by all other testers.” I don’t agree with this and the use of the term “schism” is exactly the kind of divisive language Rex was accusing CDT community members of using. Does anyone “outside” of the CDT community really “pay a price” for the existence of that community? I just don’t see it.

(The domain that Matt refers to is and it’s not being actively maintained as far as I’m aware, but it does at least give us a reference point for the principles. )

There – obviously – remain challenges for the context-driven testing community in communicating the very real value and benefits that come from testing viewed via the lens of the CDT principles. It’s great to see the continued efforts of the Association for Software Testing in this regard, with their most recent CAST conference having the theme of “bridging between communities”. I’m also proud to co-organize the AST’s Australian conference, TiCCA19, and look forward to delivering a great programme to a broad representation of the local testing community, with a focus on CDT and the value that approaches built around CDT principles offer.

1 thought on “In response to “context-driven testing” is the “don’t do stupid stuff” school of testing

  1. Pingback: Testing Bits – December 9th – December 15th, 2018 | Testing Curator Blog

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s