Enable verbose printing of exceptions thrown in junit tests #32
Conversation
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
|
I've never used JUnit with sbt, so I can't really tell. But I agree on the idea. |
|
Agree on the principle as well. LGTM. |
DarkDimius
added a commit
that referenced
this pull request
Mar 3, 2014
Enable verbose printing of exceptions thrown in junit tests
noti0na1
added a commit
to noti0na1/dotty
that referenced
this pull request
Oct 22, 2019
Revert Change about throwMethod; Clean up if-else
szymon-rd
pushed a commit
that referenced
this pull request
Dec 9, 2022
Fixed expand buttons and listeners
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.
By default sbt/junit-interface swallows exceptions without printing stack traces and exception class name.
Enabled verbose printing of exception for better understanding travis logs.