Add a command to relaunch tests but limited to the failing one(s)

[Canop]

(follows issue #213 and discussion with @GeeWee)

The idea would be to hit a key and have the same test/nextest/whatever job relaunched but scoped to the failing test(s).

Hitting escape would take you back to all tests.

[GeeWee]

That would also be incredible - just like Jest's option to only rerun failing tests!

[Canop]

A serious problem is that cargo test doesn't support specifying several tests to run. Either you run them all or you run all the ones which contain a specific string.

So if I want an easy scoping feature, it would run only when there's only one failure. Or when using nextest.

[Canop]

Tests of the PR welcome!

[GeeWee]

I did a bit of digging, and I think a potential workaround might be to:

• List all tests
• Pass the --skip FILTER argument to cargo test, skipping any test that passed from the list. It's a libtest argument that can be passed multitple times.
• All that's left should be the failing tests.

I'm not 100% if you'll run into issues with command length if you have a lot of tests, but it's at least a possible avenue.

[Canop]

@GeeWee Oh, I missed that. It's interesting.

[Canop]

Of course, nextest doesn't support it, which makes it hard to support in a generic way ^^

A skip logic is also very painful in other ways (for example it makes it impossible to serialize the mission order, or to pass it at command line) and would have to be tested on projects with thousands of tests.

So I'll probably merge the current PR as is (when scoping, you're usually interested in your new failing test anyway) and postpone using (or not) --skip. And maybe I'll have a look at cargo test to see if a PR improving it is possible.

[GeeWee]

I think that's a good call :)