Document using @Mock with method parameters
#1961
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
Although we've called it out in the [JUnit extension], we should also make sure it's clear in the core documentation to make it more visible. We can fully-quality the `@Test` annotation to make clear that it has to be with JUnit 5. Closes mockito#1960. [JUnit extension]: https://javadoc.io/doc/org.mockito/mockito-junit-jupiter/latest/org/mockito/junit/jupiter/MockitoExtension.html
Codecov Report
@@ Coverage Diff @@
## release/3.x #1961 +/- ##
=================================================
+ Coverage 85.77% 85.80% +0.02%
Complexity 2543 2543
=================================================
Files 318 318
Lines 7215 7215
Branches 861 861
=================================================
+ Hits 6189 6191 +2
Misses 810 810
+ Partials 216 214 -2
Continue to review full report at Codecov.
|
Closed
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.
Although we've called it out in the JUnit extension, we should also
make sure it's clear in the core documentation to make it more visible.
We can fully-quality the
@Testannotation to make clear that it has tobe with JUnit 5.
Closes #1960.