Context: assume that we use the tool on an .sln file that contains a lot of test (and, maybe, non-test projects).
Upon execution, tool will run dotnet test which will search for tests in all the test projects, execute them. If there are failures, the tool will re-run dotnet test on all the test projects searching for the failed tests, having a performance impact.
Would it be possible, on re-run, to run dotnet test on the test projects (or even the DLLs) that contain the failed tests?
When we think about a solution for #117 we could try to see if the solution would also match this use case.
Will try to think of something that would make sense to be supported here.
Context: assume that we use the tool on an .sln file that contains a lot of test (and, maybe, non-test projects).
Upon execution, tool will run
dotnet test
which will search for tests in all the test projects, execute them. If there are failures, the tool will re-rundotnet test
on all the test projects searching for the failed tests, having a performance impact.Would it be possible, on re-run, to run
dotnet test
on the test projects (or even the DLLs) that contain the failed tests?Thanks again for this great library!