Automatic bisect

Learn automatic testing with bisect run.

Automated bisect

Instead of testing every commit manually during a bisect search, you can run a test command with git bisect run. Git executes that command automatically on each selected revision. It uses the test's exit status to classify the commit as good or bad.

git bisect run npm test

The test command must produce reliable and repeatable results for every revision.

Test exit codes

git bisect run interprets the result using the test command's exit status. Usually, 0 indicates a successful test, while codes from 1 to 127 indicate a failure. Special exit codes are also available for cases where a test cannot be run, so configure the test command carefully.

git bisect run ./test.sh

The test script should run under consistent conditions on each revision and report its result using an appropriate exit code.

Exercise Run an automated bisect test

Assume the bisect search has started and the good/bad boundaries have already been defined. Run npm test automatically throughout the search.

Test yourself

Which option tells Git which test command to run on each commit during an automated bisect?
- git bisect log
- git bisect reset
- git bisect run
- git bisect start
Show answer

git bisect run — git bisect run automatically executes the specified test command during the search.
Run a test script automatically
```
git bisect ____
```
Show answer
```
git bisect run ./test.sh
```
Automated testing workflow

git bisect run

Runs the test command automatically
Test betiği

Checks application behavior
Çıkış kodu 0

Indicates that the test passed
Çıkış kodu 1

Indicates that the test failed

Next lesson: Summary - Bisect

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies