Ryan,

You explained clearly the problem that mintest-bisect is trying to solve ("knowing which test is failing, and the interdependence involved"). But you did not explain how it does it. From your description it is unclear what methodology is being used or what output/result of using the library is.

Thanks,

Andy

On Sat, Jul 8, 2023 at 5:48 PM Ryan Davis via ruby-talk <ruby-talk@ml.ruby-lang.org> wrote:

> On Jul 6, 2023, at 18:00, Eike Dierks via ruby-talk <ruby-talk@ml.ruby-lang.org> wrote:
>
> Hi Ryan,
>
> can you please tell us about,
> how minitest-bisect
> can help us

I did:

>> 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.

______________________________________________
ruby-talk mailing list -- ruby-talk@ml.ruby-lang.org
To unsubscribe send an email to ruby-talk-leave@ml.ruby-lang.org
ruby-talk info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-talk.ml.ruby-lang.org/