35 / 57 · 17 Git & Version Control · Bisect and Cherry-Pick← prev⊞ allnext →☰ Read as one page
5.5When to Use Bisect
| Scenario | Why Bisect Helps |
|---|---|
| A test that passed last week now fails | Find the exact commit that broke it |
| Performance regression (page load 3x slower) | Find when the slowdown was introduced |
| Visual regression (layout shifted) | Find which commit changed the CSS |
| Flaky test appeared | Find when the flakiness was introduced |
| Feature that "used to work" is broken | Prove which commit introduced the bug |
Bisect is invaluable for QA because it gives you a specific commit, author, and description to reference in your bug report. "This regression was introduced in commit abc123f by @developer on Jan 15 when they refactored coupon validation" is much more actionable than "checkout is broken."