Feature Request: --fail-slow=10

[scottconnerly]

What are you trying to achieve?

A halfway point between --fail-fast and running the full suite

Details

• -fail-fast gives quick feedback loops
• running the full suite gives all the context you need to figure out why something might be failing.

But what if there was a middle ground where, in a run where a LOT of tests were destined to fail, you still got more context on those failures than just the first one that failed? Like, maybe one could specify the number of tests that needed to fail before abandoning the rest of the suite?

Thus I propose an option called --fail-slow that after X number of tests fail, the run quits. If < X number of tests fail, the suite completes (but still returns a failure error code, of course).

[DavertMik]

Seems good but I don't like the naming, my first guess was that this should fail slow tests, i.e. tests that take a long time to run.
So I agree this feature can be implemented with an optional parameter for --fail-fast like --fail-fast=10

If you can read the source code and figure out how to implement it, I am absolutely fine accepting this pull request