Add a --failfast option to stop testing after the first failure #2290
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Whilst misleading if run from Jenkins or from a general regression point of view (where knowing about all failures is invariably more useful), bailing out on the first failure is more appropriate behaviour in a "REPL", TDD or simply a quick "hack it until the tests pass" mode of coding. Signed-off-by: Chris Lamb <chris@chris-lamb.co.uk>
mattsta
added
state-design-effort-needed
state-proposed-feature
REVIEW-AND-MERGE
and removed
state-design-effort-needed
labels
|
Just wondering if you've had any thoughts on this after a couple of years? :) |
|
Any update on this, NACK/ACK wise? |
|
Does not apply but maybe this option is already available, even if with a different semantics, that is the new |
|
Ooh. ( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Whilst misleading if run from Jenkins or from a general regression point of
view (where knowing about all failures is invariably more useful), bailing
out on the first failure is more appropriate behaviour in a "REPL", TDD or
simply a quick "hack it until the tests pass" mode of coding.
Signed-off-by: Chris Lamb chris@chris-lamb.co.uk