-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update mockito monorepo to v5 (major) #181
base: master
Are you sure you want to change the base?
Conversation
Hey! Changelogs info seems to be missing or might be in incorrect format. |
Kudos, SonarCloud Quality Gate passed!
|
f8ef661
to
390aa1f
Compare
Pull request by bot. No need to analyze |
390aa1f
to
6a2a390
Compare
6a2a390
to
fa9cc46
Compare
Kudos, SonarCloud Quality Gate passed!
|
fa9cc46
to
5848024
Compare
Kudos, SonarCloud Quality Gate passed!
|
5848024
to
ef3c7d9
Compare
ef3c7d9
to
976a159
Compare
f525bb7
to
807c97b
Compare
a36f653
to
8ea80d2
Compare
979c062
to
4da7843
Compare
4da7843
to
e7ef517
Compare
e7ef517
to
7c06589
Compare
5337fc0
to
a8ee4c6
Compare
Kudos, SonarCloud Quality Gate passed!
|
a8ee4c6
to
a470768
Compare
a470768
to
0798b60
Compare
Kudos, SonarCloud Quality Gate passed!
|
0798b60
to
b4e3e42
Compare
b4e3e42
to
623c53a
Compare
Kudos, SonarCloud Quality Gate passed!
|
623c53a
to
e674aea
Compare
Please retry analysis of this Pull-Request directly on SonarCloud. |
e674aea
to
96f6456
Compare
96f6456
to
13a499e
Compare
13a499e
to
5e3d7c5
Compare
Kudos, SonarCloud Quality Gate passed!
|
5e3d7c5
to
9c851dd
Compare
9c851dd
to
43a61b3
Compare
|
43a61b3
to
b0560f2
Compare
|
b0560f2
to
00632c5
Compare
|
This PR contains the following updates:
3.12.4
->5.12.0
3.12.4
->5.12.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
mockito/mockito (org.mockito:mockito-core)
v5.12.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.12.0
AdditionalMatchers.and()
andAdditionalMatchers.or()
not to swap the order of matchers (#3335)v5.11.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.11.0
@Captor
test parameters don't work with primitive type arguments (#3229)v5.10.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.10.0
v5.9.0
What's Changed
New Contributors
Full Changelog: mockito/mockito@v5.8.0...v5.9.0
v5.8.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.8.0
v5.7.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.7.0
0.8.11
(#3147)v5.6.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.6.0
Optional
is notempty
when usingRETURN_DEEP_STUBS
(#2865)v5.5.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.5.0
v5.4.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.4.0
@Mock(serializable = true)
for parameterized types. (#3007)ArgumentMatchers#any()
JavaDoc(#3003)
@Mock(serializable = true)
no longer works with parameterized types (#2979)v5.3.1
Changelog generated by Shipkit Changelog Gradle Plugin
5.3.1
v5.3.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.3.0
withoutAnnotations
parameter to@Mock
(#2965)ArgumentMatchers#assertArg
method. (#2949)v5.2.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.2.0
v5.1.1
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.1.1
v5.1.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.1.0
CONTRIBUTING.md
(#2870)CONTRIBUTING.md
(#2868)Mockito#{mock,spy}(T... reified)
with@SafeVarargs
(#2866)v5.0.0
Compare Source
Mockito 5: prepare for future JDK versions
For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API.
Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker.
Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working.
Switch the default mockmaker to
mockito-inline
Back in Mockito 2.7.6, we published a new mockmaker based on the "inline bytecode" principle.
This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery.
As a comparison, the subclass mockmaker generates "real" subclasses for mocks, to mimic the same behavior.
While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes.
For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass.
Massive thanks to community member @reta who implemented this change.
Note: this does not affect
mockito-android
nor testing on Android.When should I still be using the subclass mockmaker?
There are legitimate remaining use cases for the subclass mockmaker.
For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice.
Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility.
Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+.
We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker.
If you want to use the subclass mockmaker instead, you can use the new
mockito-subclass
artifact (published on Maven Central along with all our other artifacts).Update the minimum supported Java version to 11
Mockito 4 supports Java 8 and above.
Similar to other open source projects, we are moving away from JDK 8 and to newer versions.
The primary reason for moving away from JDK 8 is the increasing maintenance costs with keeping our own infrastructure working.
Lately we have been running into more and more JDK 8 breakages.
Additionally, while we want to support the newest JDK API's, our current solution to support both JDK 8 and newer versions causes issues with the
SecurityManager
.Since we want Mockito to work on the newest version and more and more businesses adopting JDK 11, we have decided to make the switch as well.
Massive thanks to community member @reta who implemented this change.
What should I do if I still run JDK 8?
For JDK 8 and below, you can keep on using Mockito 4.
This is similar to if you are using JDK 6, for which you can keep on using Mockito 2.
The changes in Mockito 5 (for now) are primarily focused on the latest JDK versions, which means the API differences between Mockito 4 and 5 are minimal.
However, over time this will most likely widen, so we do recommend adopting JDK 11 in the future.
New
type()
method onArgumentMatcher
One of our most used public API's for customizing Mockito is the
ArgumentMatcher
interface.The interface allows you to define a custom matcher, which you can pass into method arguments to provide more targeted matches.
One major shortcoming of the
ArgumentMatcher
was the lack of varargs support.There were many, many issues filed related to varargs and Mockito unable to handle them.
Community member @big-andy-coates put in a lot of effort to come up with an appropriate solution, including fully implementing and comparing 2 approaches.
Ultimately, we decided that introducing a new
type()
method onArgumentMatcher
is the best solution.As a result, it is now possible to update your custom matchers to implement varargs support, if you so desire.
Note that
ArgumentMatcher
is still a@FunctionalInterface
and can therefore still be written as a lambda.Massive thanks to community member @big-andy-coates who implemented this change.
What is the effect of this new method?
For varargs methods, there was previously a way to only match zero arguments, or two or more arguments, by using the exact number of matchers, i.e.
But following the pattern to match exactly one argument:
doesn't work, as
any
is "vararg aware", so Mockito matched theany
against each element of the varargs parameter, meaning it will match any number of arguments, i.e. the above would of matched all of these:With the new
type
method, it's now possible to differentiate matching calls with any exact number of arguments, or to match any number of arguments.Therefore, if you want to match 0 or more arguments, use
any(String[].class)
.If you want to match an exact number of arguments, use
any(String.class)
(and specify as manyany
matchers as arguments you want to match on).In a similar fashion, the behavior of
ArgumentCaptor.forClass
has changed as well.If you want to capture all arguments, use an
ArgumentCaptor
forString[]
, otherwiseString
:For more information, see the description and conversation in pull request 2835 and pull request 2807.
At the same time,
ArgumentCaptor
is now fully type-aware.This allows for capturing specific subclasses on a generic method:
Do I need to implement this new method?
No, you don't need to.
Mockito 5 declares a default implementation, returning
Void.type
as the type of anArgumentMatcher
.This essentially means that Mockito will not consider the type when handling varargs.
However, if you do return a specific type, Mockito will consider this when matching arguments.
As a result, this new method is not a source-breaking change, but is a bytecode-breaking change.
All code working on Mockito 4 should work as-is when recompiled with Mockito 5.
v4.11.0
Changelog generated by Shipkit Changelog Gradle Plugin
4.11.0
any(String[].class)
doesn't work as expected (#2796)v4.10.0
Changelog generated by Shipkit Changelog Gradle Plugin
4.10.0
MatcherApplicationStrategy
(#2803)v4.9.0
Changelog generated by Shipkit Changelog Gradle Plugin
4.9.0
v4.8.1
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
4.8.1
v4.8.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
4.8.0
v4.7.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
4.7.0
1988123
, Andy Coates, Chen Ni, Marius Lichtblau, Nikita Koselev. Developer Advocate, Open Source Ally, Rafael Winterhalter, dependabot[bot], dstango, fishautumn, heqiangConfiguration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.