Protocol
Bisect the version history instead of inspecting every change
The last edit is a suspect, not automatically the culprit.
Before you use it
- Use when
- The same test passed in an earlier version and fails now.
Keep this limit in mind
- Repeated introduction and removal of a bug, changing dependencies or flaky tests can invalidate a simple one-transition story.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Choose a reproducibly passing version and a failing version. Test a version between them, then keep the half containing the transition. Continue until the boundary is narrow enough to inspect. Git bisect automates this search for code history.
Steps
- Use the same input, test and relevant environment across versions.
- Record untestable versions as unknown, not as failures.
- Confirm the candidate boundary with a fresh run and inspect the actual change.
An example
A mapping worked in release A and breaks in H. Testing D and then F narrows the investigation without reading every transport first.
Check your result
The report names the tested boundary and any skipped versions that prevent a precise conclusion.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Try it in a task guide
These guides use this edition of the method alongside other ideas for the same task.
Bisect version history when a known-good and known-bad boundary exists.Debug an Intermittent Failure or Flaky Test
Connected ideas
You are readingBisect the version history instead of inspecting every change
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaShrink the example until the same failure is hard to hide
Evidence and sources
Git bisect narrows a known-good to known-bad version interval through repeated tests; skipped versions can leave an ambiguous boundary.
A first failing version is an investigation lead, not proof of a complete root cause.
git-bisect: Use binary search to find the commit that introduced a bug · Description; Bisect skip
Edition and review
Version 0.1.0
No review details are supplied for this edition.