minitest-bisect version 1.1.0 has been released!
Hunting down random test failures can be very very difficult,
sometimes impossible, but minitest-bisect makes it easy.
minitest-bisect helps you isolate and debug random test failures.
If your tests only fail randomly, you can reproduce the error
consistently by using
--seed <num>, but what then? How do you figure
out which combination of tests out of hundreds are responsible for the
failure? You know which test is failing, but what others are causing
it to fail or were helping it succeed in a different order? That’s
what minitest-bisect does best.
1.1.0 / 2014-09-08
4 minor enhancements:
- Added MTB_DEBUG env var to add debugging output to bisect trials.
- Added MTB_VERBOSE env var to show test output.
--server ###from final repro to make it easer to
-soption. Now only
--serverremains to be unambiguous.
3 bug fixes:
- Accidentally left in -v while I was debugging something.
- Reject skips in culprit accounting.
- Switched to manual escaping of regexp. Shellwords was horribly