This repository has been archived by the owner on Oct 10, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Update dependency org.mockito:mockito-core to v5 #957
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-mockito-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
4 times, most recently
from
January 31, 2023 15:25
002bf2a
to
b97d3a2
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
February 27, 2023 12:46
b97d3a2
to
91210e3
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
March 9, 2023 21:21
91210e3
to
709fd0f
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
April 11, 2023 23:37
709fd0f
to
6360063
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
April 21, 2023 20:29
3df4932
to
a8aeb56
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
May 22, 2023 14:59
a8aeb56
to
eb8ec54
Compare
This was referenced May 27, 2023
Closed
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
May 30, 2023 17:36
eb8ec54
to
65472c8
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
June 18, 2023 16:44
8396816
to
cbff855
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
July 5, 2023 16:19
cbff855
to
a2852e0
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
August 22, 2023 11:48
a2852e0
to
8de0618
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
September 4, 2023 14:08
8de0618
to
b2848f3
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
September 23, 2023 11:49
b2848f3
to
303c1f9
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
October 6, 2023 15:41
303c1f9
to
440fe05
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
October 30, 2023 18:49
8ab6f15
to
5091aa1
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
November 2, 2023 22:13
5091aa1
to
d07eac6
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
December 1, 2023 23:13
10c69f6
to
7168ba4
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
3 times, most recently
from
December 24, 2023 16:35
48235f1
to
fe6ff09
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
January 16, 2024 19:17
0ab24c9
to
d570a84
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
January 24, 2024 21:07
cb5b522
to
ebc99fe
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
February 2, 2024 19:38
ebc99fe
to
2818497
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
February 16, 2024 19:12
2818497
to
dcb9bc2
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
March 1, 2024 09:38
d98f706
to
284db7d
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
April 20, 2024 11:52
284db7d
to
21b85ba
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
May 11, 2024 11:34
21b85ba
to
8a6c941
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
June 25, 2024 18:42
59346dd
to
9834b9e
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
June 27, 2024 19:29
9834b9e
to
44a18c5
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
July 12, 2024 23:42
44a18c5
to
0b0876f
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
August 27, 2024 22:51
c177e2d
to
3123855
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
September 30, 2024 12:50
91ee2a9
to
93bb03e
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
October 10, 2024 21:02
93bb03e
to
a2f33e5
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
0 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.
This PR contains the following updates:
4.11.0
->5.14.1
Release Notes
mockito/mockito (org.mockito:mockito-core)
v5.14.1
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.1
v5.14.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.0
v5.13.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.13.0
Only.verify
throwsNullPointerException
(#3237)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
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.10.0
v5.9.0
Compare Source
What's Changed
New Contributors
Full Changelog: mockito/mockito@v5.8.0...v5.9.0
v5.8.0
Compare Source
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
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 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 parConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.