Using JUnit rules to test exceptions #814
Merged
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
|
This pull request will allow us to write tests with few line codes, using a modern and fluent API, catching the properly exceptions (both exception instance and message and not a generic exception type only), and the code will more clear. Based on this facts, I'll merge even this pull request received no comments. Thank you devs. |
garcia-jj
added a commit
that referenced
this pull request
Sep 24, 2014
Using JUnit rules to test exceptions
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.
First attempt to use JUnit exception rules. Related to #808.
Since this is not affect dist artifacts, I think that can merged without wait new release.