It's a tough time to focus on tech. We, the Mockito team, stand with Ukraine. If you can help, please do! helpukrainewin.org

Mockito 4.1.0 ships a new major feature: `@DoNotMock`. You can now mark classes/interfaces with @org.mockito.DoNotMock to disallow mocking with Mockito. For more information, see our documentation: javadoc.io/doc/org.mockito/m…

Yes, for now you will still require to specify the separate inline mockmaker. We are still monitoring the evolution in the JDK and how that affects the older subclass mockmaker before we are changing the default. Therefore, Mockito 4 didn't change the default just yet.

We have just published Mockito 4.0.0 to Maven Central! The 4.0.0 release removes all previously deprecated APIs. There are no other breaking changes or otherwise functional changes compared to Mockito 3.12.4 For an overview of now removed APIs, please see github.com/mockito/mockito/r…

Are you an Android developer who uses Mockito? To avoid regressions for our Android users, we are looking to add a small regression test suite (our 3.11.x releases had several issues). If you would like to contribute to open source, the place to start is github.com/mockito/mockito/i…

We want to thank @n_haarman for the original idea, creation and maintenance of mockito-kotlin.

The mockito-kotlin artifact has migrated to the Mockito GitHub organisation and is now published at "org.mockito.kotlin:mockito-kotlin" on Maven Central. We also published version 3.0.0 that upgrades to Mockito 3 and migrates to ArgumentMatchers: github.com/mockito/mockito-k…

Please note that we don't publish all releases to Maven Central. We tend to publish to the central repository about once a month. Publishing releases to a separate repository aids in triaging and obtaining early feedback from users who do use new releases immediately.

Please be aware of future JDK releases that can break your test if you are using `mockito-core`. Mockito is ready for the future with the `mockito-inline` artifact, which enables the future-proof inline mockmaker. We recommend switching the artifact if you run into these issues.

Mockito is now fully ready for the future.

For more background on this change and the full journey we have gone through, please read the corresponding issue (with a lot of comments/thoughts/concerns/ideas): github.com/mockito/mockito/i…

We are looking for feedback on a prototype for mocking of static methods. We want to promote a constrained, yet powerful API, in favor of looser API contracts. The current prototype (by design) limits static method mocking to a small scope, but would stub nonetheless.

Mockito is ready for Java 14. Are you?

Mockito is now funded via Tidelift such that we receive a monthly income for the framework. As a group, we decided to donate this money to a charity and are looking forward to sending 400 dollars monthly to Save the Children. Thank you everyone for contributing!

Mockito relies on ByteBuddy to generate mocks. We have seen a lot of improvements over the CGLibMockmaker thanks to the hard work of Rafael. Please consider sponsoring his work if you are Mockito user.

Good catch. We indeed forgot to update that page. Will get to it today!

JUnit5 is already building with Mockito 3. Let us know about your successful and not-so-successful migrations!

We just published Mockito 3 to Maven Central!

We are aware of an issue with the mockito-core 2.27.5 which was not published to Maven Central. Maven Central appears to be in a corrupt state for this artifact. We have contacted the Nexus repository maintainers and requested a solution.

After a short beta period, provided no issues arise, we will publish Mockito 3 to Maven Central. For now, you can find the beta releases at Bintray: bintray.com/mockito/maven/mo…