Most popular Mocking framework for unit tests written in Java
Most popular mocking framework for Java
Still on Mockito 1.x? See what’s new in Mockito 2!
Mockito 3 does not introduce any breaking API changes, but now requires Java 8 over Java 6 for Mockito 2.
Mockito 4 removes deprecated API.
Mockito 5 switches the default mockmaker to mockito-inline, and now requires Java 11.
Only one major version is supported at a time, and changes are not backported to older versions.
Available as part of the Tidelift Subscription.
The maintainers of org.mockito:mockito-core and thousands of other packages are working with Tidelift to deliver
commercial support and maintenance for the open source dependencies you use to build your applications. Save time,
reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use.
Learn more.
Mockito publishes every change as a -SNAPSHOT
version to a public Sonatype repository. Roughly once a month, we
publish a new minor or patch version to Maven Central. For release automation we use
Shipkit library, Gradle Nexus Publish Plugin.
Fully automated releases are awesome, and you should do that for your libraries, too!
See the latest release notes
and latest documentation. Docs in
javadoc.io are available 24h after release. Read also
about semantic versioning in Mockito.
Older 1.x and 2.x releases are available in
Central Repository
and javadoc.io (documentation).
All you want to know about Mockito is hosted at The Mockito Site which is Open Source and likes pull requests, too.
Want to contribute? Take a look at the Contributing Guide.
Enjoy Mockito!
To build locally:
./gradlew build
You can open in any IDE that support Gradle, e.g. IntelliJ IDEA, or Fleet.
For Eclipse, one may need to run ./gradlew eclipse
before importing the project.
Every change on the main development branch is released as -SNAPSHOT
version to Sonatype snapshot repo
at https://s01.oss.sonatype.org/content/repositories/snapshots/org/mockito/mockito-core.
To release a non-snapshot version to Maven Central push an annotated tag, for example:
git tag -a -m "Release 3.4.5" v3.4.5
git push origin v3.4.5
At the moment, you may not create releases from GitHub Web UI. Doing so will make the CI build fail because the
CI creates the changelog and posts to GitHub releases. We’ll support this in the future.