Heuristic

Bisect the search without guessing untestable results

Split a large search into two meaningful parts, then test which part still contains the problem. The result must narrow the same question each time.

About 2 min read

Before you use it

Use when
  • The searchable space is ordered or divisible and checking every candidate one by one would be expensive.

Keep this limit in mind

  • Do not use bisection when candidates interact non-monotonically, the midpoint cannot be tested or the failure classification is unstable.

Current editorial reading

Keep one question fixed

For a component chain or processing pipeline, inspect a boundary that separates the remaining possibilities. Continue within the implicated part only when the result justifies it. For revision history, start from known old and new behavior and test between them. Keep the criterion and relevant environment stable. If behavior changes back and forth or tests are unreliable, investigate before trusting a single boundary.

Handle untestable revisions honestly

In Git history, an unrelated build failure is not a result for the bug under investigation. Git can skip that revision and choose another. For example, a missing build dependency may prevent testing a data-corruption regression. Skips near the transition can leave several possible first-bad commits. This is Git’s supported behavior; a different system needs its own valid way to handle an untestable split.

Take it with you

Keep the test log and report the implicated component or revision, or the unresolved candidate set. Do not force an uncertain result into a clean division.

Sources and evidence (2)

What we checked

Supports

Git supports skipping revisions that cannot be tested.

Selected versioned documentation inspected on 2026-10-04. This corrects the original blanket prohibition on an untestable midpoint.

git-bisect Documentation, version 2.52.0 · Version 2.52.0; Avoiding testing a commit; Bisect skip

Limits

Skipping commits near the transition can prevent identification of one exact first-bad commit.

The uncertainty must remain in the output; an unrelated build failure is not a target-test result.

git-bisect Documentation, version 2.52.0 · Version 2.52.0; Bisect skip

Provides context

System bisection is an operational divide-and-conquer technique.

Selected official passage inspected. It does not establish that all system failures or revision histories have one clean transition.

Effective Troubleshooting · Simplify and reduce

Editorial sources (2)

Editorial version 1.0.0 · Evidence checked 2026-10-04

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Try it in a task guide

These guides use this edition of the method alongside other ideas for the same task.

Bisect a valid ordered failure domain.
Debug an Intermittent Failure or Flaky Test

Connected ideas

You are readingBisect the search without guessing untestable results

Original edition evidence and sources

These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.

Supports

Google SRE describes bisection as repeatedly splitting a large system in half to narrow a possibly faulty component; Git bisect applies binary search to ordered revision history.

Bisection needs a meaningful ordered search space and a reasonably testable distinction between the two states.

Effective Troubleshooting · Simplify and reduce; bisection

All sources (1)
Original edition, downloads and provenance

The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.

Version 0.1.0

No review details are supplied for this edition.

Read the original edition and overlay as JSON · Release details