Test improvement: removed Exception Handling (test smell)#292
Open
eas5 wants to merge 1 commit into
Open
Conversation
Codecov Report
@@ Coverage Diff @@
## master #292 +/- ##
=========================================
Coverage 96.16% 96.16%
Complexity 920 920
=========================================
Files 56 56
Lines 2320 2320
Branches 369 369
=========================================
Hits 2231 2231
Misses 48 48
Partials 41 41 Continue to review full report at Codecov.
|
Owner
|
Looks good...minor issue is the comments are re-formatted. Maybe I should put in a shortened or blanket license. |
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
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.
This is a test refactoring.
Problem:
The Exception Handling test smell occurs when a test method explicitly a passing or failing of a test method is dependent on the production method throwing an exception.
Solution:
Use JUnit's exception handling to automatically pass/fail the test instead of writing custom exception handling code or throwing an exception. In this case, JUnit 4.13 assertThrows() was used to properly handle the expected exception.
Result:
Before:
After: