new FailReporter#308
Merged
Merged
Conversation
added 4 commits
October 4, 2015 20:45
single purpose: fail at end if any errors or failures were detected
Member
Author
|
This works best with #307 ( |
Member
Author
|
Probably this should be default behavior for all reporters. Think about implementing that logic in the code that calls end_reporter(). |
Member
Author
|
Merged with master. Should the StopReporter stop after the first event (error/failure/warning), and not wait until the end of the test? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
single purpose: fail at end if any errors or failures were detected
Difference to StopReporter: The latter stops immediately, the new reporter proceeds until end of tests.