1
Explaining Testing to
Anybody
James Bach, Satisfice, Inc.
James@satisfice.com
www.satisfice.com
Uh oh…
How do you respond when someone
you work with doesn’t understand
how testing works?
2
head… heavy…
strength… fading…
zzzzzzzz…
“In the testing process, test plans are made,
test cases specified, tests databases and
files set up, test output created, and so on.
It is important to regard this testware not as
a disposable product, but as one that has to
be filed, managed, and handed over for
reuse upon—are you listening?”
Basics of Explaining
Be quick, then stop and check in.
Be humble. Exceptions and alternatives abound.
You can be wrong, as long as you’re thoughtful.
Be real. Own the explanation.
Be respectful. Honor objections and questions.
Be patient. Often, experience must come first.
Be relevant. How does it relate to them? What’s
the bottom-line? What do you want them to do?
3
Basics of Explaining
Be prepared
− Quick point (a few sentences at most.)
− Simile & Metaphor (relate to something familiar)
− Vocabulary check (are you using words the same way?)
− 5-minute whiteboard talk (diagrams are powerful)
− Concrete examples or demonstration (in-house data)
− Anticipate common questions and objections
− References & supporting material (have it handy)
Explanations
Confusions
− “What is testing?”
− “What’s so hard about testing?”
− “How do you know when you’re done?”
− “Why didn’t you find that bug?”
“Let’s {do my crazy plan},okay?”
− “…change the product at the last minute…”
− “…specify those tests in advance [and automate them]…
4
“What is Testing?”
Quick points (choose one):
− Testing is organized skepticism. It’s the belief that things
may not be as they seem; that things could be different.
− Testing is comparing the ambiguous to the invisible, so as
to avoid the unthinkable happening to the unknown.
− Testing brings vital information to light, so we can see
where we are and make better decisions.
− Testing is a support function that helps developers look
good by finding their mis