Extending/organizing MatchersTest.kt #548
Merged
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
…in the Methods test interface. Also, organized MatchersTest.kt with nested test classes.
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.
Towards fixing #492.
I was on my way to add tests for unsigned integers, but then I found the test class
MatchersTestlacking test coverage for many types already included in the Methods test interface. So I have added missing tests for any(), anyOrNull() and eq() matchers.As the number of tests in the test class is growing, I have started to organize the tests by introducing nested test classes (in JUnit4 style).
All existing test cases still remain in the class but may have moved to the related nested test class, and test methods may have been adjusted slightly to allign with sibling tests in the same nested test class.