-
-
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) #43
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. |
bd402d9
to
6209350
Compare
6209350
to
9c7b355
Compare
Pull request by bot. No need to analyze |
dd94e5d
to
cf633de
Compare
3e270cf
to
3f36401
Compare
fe4800f
to
4437a14
Compare
4437a14
to
14890cb
Compare
903daeb
to
9bbd18c
Compare
066c6a5
to
b61ff99
Compare
e3ececb
to
82bf51a
Compare
82bf51a
to
219e546
Compare
807ad86
to
1b62ac5
Compare
1b62ac5
to
9a6b95a
Compare
9a6b95a
to
0107f4d
Compare
cc7c252
to
d70920d
Compare
2b72fca
to
1093a67
Compare
1093a67
to
a8a7191
Compare
a8a7191
to
5158673
Compare
5158673
to
1e642fd
Compare
1e642fd
to
29f4f46
Compare
29f4f46
to
b9b35fe
Compare
b9b35fe
to
4864b12
Compare
4864b12
to
bdba743
Compare
bdba743
to
31e6b54
Compare
31e6b54
to
b714183
Compare
b714183
to
5afd333
Compare
5afd333
to
4351d01
Compare
4351d01
to
a213a90
Compare
a213a90
to
b92c4b0
Compare
b92c4b0
to
f7078d5
Compare
f7078d5
to
bf4d3a6
Compare
bf4d3a6
to
43cf1c6
Compare
43cf1c6
to
dd85d19
Compare
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: maven/org.mockito/[email protected], maven/org.mockito/[email protected] |
1eefa3b
to
c22c8ca
Compare
c22c8ca
to
b19dee4
Compare
This PR contains the following updates:
3.12.4
->5.14.2
3.12.4
->5.14.2
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
mockito/mockito (org.mockito:mockito-core)
v5.14.2
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.2
mockito-
prefix (#3460)v5.14.1
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.1
v5.14.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.0
v5.13.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.13.0
Only.verify
throwsNullPointerException
(#3237)v5.12.0
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
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
Changelog generated by Shipkit Changelog Gradle Plugin
5.7.0
0.8.11
(#3147)v5.6.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.6.0
Optional
is notempty
when usingRETURN_DEEP_STUBS
(#2865)v5.5.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.5.0
v5.4.0
Compare Source
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
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.3.1
v5.3.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.3.0
withoutAnnotations
parameter to@Mock
(#2965)ArgumentMatchers#assertArg
method. (#2949)v5.2.0
Compare Source
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 soluti
Configuration
📅 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.