New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #1853: Allow @MockitoSettings to be inherited #1854
Fixes #1853: Allow @MockitoSettings to be inherited #1854
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a regression test in the junit-jupiter-test testsuite?
Codecov Report
@@ Coverage Diff @@
## release/3.x #1854 +/- ##
==============================================
Coverage 86.87% 86.87%
Complexity 2518 2518
==============================================
Files 314 314
Lines 6620 6620
Branches 831 831
==============================================
Hits 5751 5751
Misses 671 671
Partials 198 198 Continue to review full report at Codecov.
|
fe3a45b
to
e90eba6
Compare
I've just amended the commit with a test |
e90eba6
to
540c7c5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 more nit.
private Function<Integer, String> rootMock; | ||
|
||
@Test | ||
void should_throw_an_exception_on_strict_stubs_configured_by_default() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: test name should be updated to state that it properly inherits from the MockitoSettings on the superclass.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
540c7c5
to
9c0bce0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
including project members to get a better picture of the change
commit is meaningful and help the people that will explore a change in 2 years
Fixes #<issue number>
in the description if relevantFixes #<issue number>
if relevant