Welcome to the Power Users community on Codidact!
Power Users is a Q&A site for questions about the usage of computer software and hardware. We are still a small site and would like to grow, so please consider joining our community. We are looking forward to your questions and answers; they are the building blocks of a repository of knowledge we are building together.
Post History
Inspired by this comment thread, is there a way to automate git bisect with a new test (and a known good state)? The way things usually work for me is… Oh no! Reproducible bug is found. (Manual...
#1: Initial revision
by
Michael
·
2023-10-25T14:57:48Z (about 1 year ago)
Automated Git bisect
Inspired by [this comment thread](https://powerusers.codidact.com/comments/thread/8712), is there a way to automate `git bisect` with a new test (and a known good state)? The way things usually work for me is…
- Oh no! Reproducible bug is found.
- (Manually) find a release where it wasn't present.
- `git bisect` and flag the identified starting/ending commits as good/bad behavior.
- Git suggests commits to build and test, and asks me to flag them as good or not.
+ Repeat this step Log(O) times.
- Git points to a commit where the bug was introduced.
What I want to do is this…
- Oh no! Reproducible bug is found.
- Write a unit test to identify the problem.
- Find a release where the bug wasn't present.
+ Maybe manually. Maybe this can be automated, too?
- `git bisect` and flag the identified starting/ending commits as good/bad behavior.
- Git suggests commits to build and test.
+ Some process builds the code and _runs my new unit test_ to flag the suggested commits as good or bad.
- Git points to a commit where the bug was introduced.
Can I set up a system where I can provide these inputs and find out what commit is the culprit?
- The build script
- The test runner
- The new unit test (stored somehow: Stash? New commit? Just on disk somewhere?)
- The "bad" commit
- (If necessary) the "good" commit