Most popular Mocking framework for unit tests written in Java
Branch: release/2.x
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.dependabot Automatic dependency update with Dependabot (#1600) Feb 11, 2019
.github Fixed a broken link in Jul 23, 2018
config/checkstyle Enable Checkstyle for checking license headers (#1242) Nov 5, 2017
doc 2.24.5 release (previous 2.24.4) + release notes updated by CI build … Feb 18, 2019
gradle Return null instead of causing a CCE (#1612) Feb 12, 2019
src Fixes #1618 : Fix strict stubbing profile serialization support. (#1620) Feb 13, 2019
subprojects Fix issue with mocking of java.util.* classes (#1617) Feb 11, 2019
.checkstyle Additional line ending fixes Jun 6, 2015
.editorconfig Add editor config to automatically adhere to code style guide (#966) Feb 28, 2017
.gitattributes Add .gitattributes to enforce LF Jun 4, 2015
.gitignore Enable gradle build cache Nov 26, 2018
.travis.yml Simplify travis.yml (openjdk10 and openjdk11) (#1560) Dec 4, 2018
LICENSE added refEq matcher based on reflectionEquals from apache commons lang Jan 27, 2008 Merge pull request #1290 from mockito/sf Feb 15, 2018
build.gradle Try to fix Javadoc generation on Java 11 Jan 28, 2019
dummy-commit.txt Trigger build for [ci-release 2.1.0] Oct 3, 2016 Bumped Gradle to last 4.x Nov 27, 2018
gradlew Update Gradle version Jan 22, 2018
gradlew.bat update gradle (v3.5) (#1099) May 28, 2017
settings.gradle Add simple test to test the Mockito module system Jan 8, 2019 2.24.5 release (previous 2.24.4) + release notes updated by CI build … Feb 18, 2019


Most popular mocking framework for Java

Build Status Coverage Status MIT License

latest release Bintray Maven Central Javadocs

Current version is 2.x

Still on Mockito 1.x? See what's new in Mockito 2!

Mockito continuously delivers improvements using Shipkit library ( See the latest release notes and latest documentation. Docs in are available 24h after release. Read also about semantic versioning in Mockito.

Older 1.x releases are available in Central Repository , Bintray and (documentation).

More information

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!

Need help?

How to develop Mockito?

To build locally:

 ./gradlew build

To develop in IntelliJ IDEA you can use built-in Gradle import wizard in IDEA. Alternatively generate the importable IDEA metadata files using:

 ./gradlew idea

Then, open the generated *.ipr file in IDEA.

How to release new version?

Mockito implements Continuous Delivery model. Every change on main branch (for example merging a pull request) triggers a release build on Travis CI. The build publishes new version if specific criteria are met: all tests green, no 'ci skip release' used in commit message, see the build log for more information. Every new version is published to "mockito/maven" Bintray repository. New versions that Mockito team deems "notable" are additionally published to Maven Central and JCenter. We used to publish every version to Maven Central but we changed this strategy based on feedback from the community (#911).

  • Q: What's new in Mockito release model?

    A: In Q2 2017 we implemented Mockito Continuous Delivery Pipeline 2.0. Not every version is published to Maven Central.

  • Q: How to publish to Maven Central?

    A: Include "[ci maven-central-release]" in the merge commit when merging the PR. Hint: To signify a new feature consider updating version to next minor/major, like: "2.8.0", "2.9.0", "3.0.0".

  • Q: How to promote already released version to a notable version?

    A: It isn't automated at the moment. What's the use case?