Principle

Prefer a test that kills hypotheses

A test that can only confirm your favorite story is a weak detective.

About 1 min read

Before you use it

Use when
  • The investigation has accumulated several plausible stories and more logs are not narrowing them.

Keep this limit in mind

  • Operational tests may be confounded or only suggestive; preserve uncertainty when the result is not decisive.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Choose the next test for discrimination: ask which result would make one or more hypotheses much less plausible. Write the competing explanations before the test and predict what each would produce. A useful negative result can be progress because it shrinks the search space.

An example

Use the application's own database credentials to distinguish an authorization failure from a more general connectivity failure.

Check your result

Before running the test, you can state at least one result that would change what you investigate next.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingPrefer a test that kills hypotheses

Evidence and sources
Supports

Google SRE advises designing tests that can rule groups of hypotheses in or out when possible.

Many operational tests are only suggestive; uncertainty should remain visible rather than being forced into a binary verdict.

Effective Troubleshooting · Test and Treat; test design considerations

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details