NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Maven Central
Maven Central, #693 by repository stars
Mockito mock objects library core API and implementation
Latest stable
5.24.0
Last release 1 months ago
24 Sep 2026
Release timing varies
gaps range from 2 weeks to 7 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
19 years old
350 releases · first in 2008
Drag across the ruler to compare, or tap a release to open it.
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
toString() is not implemented (#3844)@Spy annotation (#3835)@Spy (#2740)Your coding agent can read these notes before it upgrades. Set up the MCP server →
The mockito-android artifact has a breaking change: tests now require a device or emulator based on API 28+ (Android P). This is to enable new support…
The mockito-android artifact has a breaking change: tests now require a device or emulator based on API 28+ (Android P). This is to enable new support for mocking Kotlin classes. See #3788 for more details.
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
Mockito.when @Nullable (#3503)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
object singletons (#3652)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
mockito-inline should be modified. (#3621)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
--info to diagnose closeAndReleaseStagingRepositories issues (#3567)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
mockito- prefix (#3460)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
Only.verify throws NullPointerException (#3237)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
AdditionalMatchers.and() and AdditionalMatchers.or() not to swap the order of matchers (#3335)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
@Captor test parameters don't work with primitive type arguments (#3229)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
Bump com.diffplug.spotless from 6.23.2 to 6.23.3 by @dependabot in https://github.com/mockito/mockito/pull/3191
Full Changelog: https://github.com/mockito/mockito/compare/v5.8.0...v5.9.0
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
0.8.11 (#3147)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
Optional is not empty when using RETURN_DEEP_STUBS (#2865)Fix Gradle 8.2 deprecation of Conventions in nexus plugin.
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
@Mock(serializable = true) for parameterized types. (#3007)ArgumentMatchers#any() JavaDoc
(#3003)@Mock(serializable = true) no longer works with parameterized types (#2979)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
withoutAnnotations parameter to @Mock (#2965)ArgumentMatchers#assertArg method. (#2949)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
CONTRIBUTING.md (#2870)CONTRIBUTING.md (#2868)Mockito#{mock,spy}(T... reified) with @SafeVarargs (#2866)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…
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.
mockito-inlineBack 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.
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).
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.
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.
type() method on ArgumentMatcherOne 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 on ArgumentMatcher 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.
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.
long call(String... args);
// Will match calls with exactly zero arguments:
when(mock.call()).thenReturn(0L);
// Will match calls with exactly two arguments:
when(mock.call(any(), any())).thenReturn(0L);
But following the pattern to match exactly one argument:
when(mock.call(any())).thenReturn(0L);
doesn't work, as any is "vararg aware", so Mockito matched the any 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:
mock.call();
mock.call("a");
mock.call("a", "b");
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.
// Match any number of arguments:
when(mock.call(any(String[].class))).thenReturn(1L);
// Match invocations with no arguments:
when(mock.call()).thenReturn(1L);
// Match invocations with exactly one argument:
when(mock.call(any())).thenReturn(1L);
// Alternative to match invocations with exactly one argument:
when(mock.call(any(String.class))).thenReturn(1L);
// Match invocations with exactly two arguments:
when(mock.call(any(), any())).thenReturn(1L);
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 many any 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 for String[], otherwise String:
// Will capture 1 string
@Captor private ArgumentCaptor<String> captor;
// Will capture all strings
@Captor private ArgumentCaptor<String[]> captor;
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:
// Given:
int simpleMethod(Collection<?> arg);
// When:
mock.simpleMethod(Set.of());
mock.simpleMethod(List.of());
// Then:
ArgumentCaptor<Collection<?>> captor = ArgumentCaptor.forClass(List.class);
verify(mock).simpleMethod(captor.capture());
assertThat(captor.getAllValues()).containsExactly(List.of());
No, you don't need to.
Mockito 5 declares a default implementation, returning Void.type as the type of an ArgumentMatcher.
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.
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
any(String[].class) doesn't work as expected (#2796)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
MatcherApplicationStrategy (#2803)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
Strictness.STRICT_STUBS (#2679)ClassCastException in AnswerFunctionalInterfaces (#2644)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
@MockitoSettings ignored after upgrade from 4.5.1 to 4.6.0 (#2656)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
net.bytebuddy.utility.GraalImageCode exceptionIf you encounter any issues with missing ByteBuddy classes, make sure you are using ByteBuddy 1.12 or higher.
Deprecate ListUtil and Fields classes
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
mockito-core to the BOM (#2550)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
@link (#2535)ExpectedException from internal test suite (#2510)*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
mockStatic (#2506)You can now mark classes/interfaces with @org.mockito.DoNotMock to disallow mocking with Mockito. For more information, see our documentation: https:/
@DoNotMockYou can now mark classes/interfaces with @org.mockito.DoNotMock to disallow mocking with Mockito. For more information, see our documentation: https://javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/DoNotMock.html
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
All of these APIs have been marked as deprecated and have been present in Mockito for quite a while.
All of these APIs have been marked as deprecated and have been present in Mockito for quite a while.
An overview of now-deleted classes/methods:
org.mockito.Matchers which was an alias for
org.mockito.ArgumentMatchersorg.mockito.ArgumentMatchers#{anyObject,anyVararg} both which were
aliases for org.mockito.ArgumentMatchers#anyorg.mockito.ArgumentMatchers#any*Of, which were aliases for the same
method name without the Of and the generic parameters (which were
ignored)org.mockito.ArgumentMatchers#{is}{Not}Null(Class) which took a class
which was ignored. Aliases for the same methods without the parameterorg.mockito.MockedStatic#verify which had the parameter types reversedorg.mockito.Mockito#verifyZeroInteractions an alias of
verifyNoMoreInteractionsorg.mockito.Mockito#debug framework integration API that we later
refactoredorg.mockito.configuration.AnnotationEngine which was leaking internal
APIs and instead users should use org.mockito.plugins.AnnotationEngineorg.mockito.exceptions.verification.TooLittleActualInvocations fixed
the grammar from "Little" to "Few"org.mockito.plugins.InstantiatorProvider which was leaking internal
APIs and instead users should use InstantiatorProvider2 (we should
probably rename back to remove the number in a future major release)org.mockito.runners a package that hosted several old JUnit runners
which were no longer supported. Users should instead use
org.mockito.junit.MockitoJUnitRunner which is our official JUnit4
runner.*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
*Changelog generated by Shipkit Changelog Gradle Plugin*
<sup><sup>Changelog generated by Shipkit Changelog Gradle Plugin</sup></sup>
One column per quarter.