Scribd
Upload
66 views

Explaining Testing To Anybody

Testing involves creating test plans, cases, databases and files to systematically evaluate a product for defects. While testware is created for each test cycle, it is important for it to be managed and reused across iterations. When explaining testing to others, it is best to be concise yet check for understanding, provide relevant examples, and anticipate questions. Key challenges in explanations include defining what testing is, why it is difficult, when it is complete, and handling questions about missed bugs or proposed changes. Using analogies, diagrams and acknowledging different perspectives can help address these challenges.

Uploaded by

Andre Choi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
66 views

Explaining Testing To Anybody

Testing involves creating test plans, cases, databases and files to systematically evaluate a product for defects. While testware is created for each test cycle, it is important for it to be managed and reused across iterations. When explaining testing to others, it is best to be concise yet check for understanding, provide relevant examples, and anticipate questions. Key challenges in explanations include defining what testing is, why it is difficult, when it is complete, and handling questions about missed bugs or proposed changes. Using analogies, diagrams and acknowledging different perspectives can help address these challenges.

Uploaded by

Andre Choi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

Explaining Testing to Anybody

James Bach, Satisfice, Inc. [email protected] www.satisfice.com

Uh oh

How do you respond when someone you work with doesnt understand how testing works?

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 uponare

you listening?
head heavy strength fading zzzzzzzz

Basics of Explaining
Be quick, then stop and check in. Be humble. Exceptions and alternatives abound. You can be wrong, as long as youre 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? Whats the bottom-line? What do you want them to do?

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? Whats so hard about testing? How do you know when youre done? Why didnt you find that bug?

Lets {do my crazy plan},okay?


change the product at the last minute specify those tests in advance [and automate them]

What is Testing?
Quick points (choose one):
Testing is organized skepticism. Its 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 mistakes before anyone else does.

What is Testing?
Similes and Metaphors
Police patrol (scanning for trouble in a complex world) Secret Service (making risky activities safer) Radar (threat detection while avoiding false alarms) Copy editing (saving authors from embarrassment) Soccer/hockey defense (we defend the goal) Science (conjecture and refutation)

What is testing?

Project Environment

Test Techniques Quality Criteria Perceived Quality Product Elements

What is testing?
Logistics
Problem Project
Environment

Oracle
Problem
Quality Criteria

Coverage
Problem

Test Techniques

Product Elements

Reporting

Perceived Problem Quality

What is testing?
Supporting Material
http://www.kaner.com/imposs.htm
Explains the impossibility of complete testing.

http://www.satisfice.com/articles/test_automation_snake_oil.pdf http://www.kaner.com/lawst1.htm
Explain the challenges of regression test automation.

http://www.satisfice.com/articles/good_enough_testing.pdf
Explains testing in the context of how much is enough.

http://www.rstcorp.com/marick/classic/mistakes.html
A gold mine of marvelous little explanations.

Explanation Hint

Try highlighting one key dynamic, instead of explaining the whole issue.

Whats so hard about testing?


smoke testing

Data
reliability testing

Functions

function testing

risk testing

Explanation Hint

Try beginning by explaining things in terms of the mission, then get more concrete from there.

How do you know when youre done?


1. When management has enough information to make an informed decision about the benefits and risks associated with the product.
AND

2. Management decides to release or cancel the project.


Both must be true or testing isnt done.

Explanation Hint

Use a diagram that helps you examine different scenarios and issues as part of the dialog.

How do you know when youre done?


Test Cycle Convergence
Good Enough Quality

Tests failed: known bad

Quality

Cycle Start

Cycle End

Build

}
Time

Tests not run: Unknown

Untestable Quality

Tests passed: known good

How do you know when youre done?


Partial Convergence:
due to incomplete test suite

Quality

Time

How do you know when youre done?


Slow Convergence:
due to inefficient testing or low testability

Quality

Time

How do you know when youre done?


No Convergence:
due to interrupted test cycle

Quality

Time

10

How do you know when youre done?


High-Biased False Convergence:
due to blissful optimism or misunderstanding of good enough

Quality

Time

How do you know when youre done?


Low-Biased False Convergence:
due to negative attitudes or misunderstanding of good enough

Quality

Time

11

Explanation Hint

Be ready to explain things from more than one angle, in case they arent receptive to your first try.

Why didnt you find that bug?


Highway Patrol analogy: Do you realize
how hard it would be to patrol the highways so that all speeders are always caught?

Risk-based improvement argument: Our goal is


to find important problems fast. Was that bug important? Could we economically have anticipated it? If so, well modify our approach.

Testability reframe: We didnt find it because the


developers didnt make the bug obvious enough for us to notice. The developers should put better bugs into the code. Lets make a more testable product.

12

Responding to Crazy Plans


Discover the need that motivates their plan. Honor something good in it. Its good practice to
find points in favor even of those things you dont believe.

Say something like


Im confused about your idea. Let me explain my confusion and then you can help me see how your plan would work. I dont know how to do what you propose without also creating the following problems Im concerned about your proposal, because I havent yet seen it work. What I have seen work is this

Then, explain the issue as you see it.

Explanation Hint

Use analogies that come from everyday experience, when you can. Then you can appeal to common sense.

13

change the product at the last minute


Driving analogy
When on the freeway, go 65mph. When on a suburban artery, go 40mph. When in a neighborhood, go 25mph. When in a parking lot, go 5mph. Park very slowly. More risks, lower speeds.

Change Control Funnel


The closer you are to shipping, the more reluctantly you should change code. To minimize retesting, carefully review proposed changes. You can change what you like, but change may invalidate everything we thought we knew about quality.

tim

Explanation Hint

It helps to validate the crazy plan even while youre opposing it. For one thing, no plan is totally crazy. For another, its how they know you understand it.

14

specify those tests in advance [and automate them]

mines

specify those tests in advance [and automate them]

mines

fixes

15

specify those tests in advance [and automate them]

mines

fixes

specify those tests in advance [and automate them]

mines

fixes

new mines

16

specify those tests in advance [and automate them]


Mine clearing analogy
To avoid mines, repeat steps exactly. A repeatable test strategy can minimize the chance that youll discover new problems. A variable test strategy will at least not avoid finding bugs.

Principle of diverse half-measures


Its usually better to do many different test techniques than it is to do one technique really well. Maximize diversity in all dimensions your testing, if you want to find more problems and uncover more risks.

Kaners Tour Bus: A test script is just a tour bus. Dont


fall asleep on the bus. Get off and look around.

Explanation Hint

The success of your explanations ultimately rests on your passion, your curiosity, and your humanity, not on your logic.
(still logic helps)

17

You might also like