MockitoJava

Tasty mocking framework for unit tests in Java

[MockitoJava @MockitoJava]

We just published Mockito 3 to Maven Central!

[@bricedutheil.bsky.social 🦋 🇪🇺🇺🇦💉 @BriceDutheil]

Congrats to the active maintainers of @MockitoJava for shipping version 3.0.0, this version one is _only_ about making Java 8 the minimum requirement. New work can now leverage many improvement in the language and JDK API that shipped since Java 6.
https://t.co/h9JO4ndVGq

[Tim van der Lippe @TimvdLippe]

Currently, all PRs to @MockitoJava are blocked because of a Java 8 build issue. Are you looking to contribute to an open source project? I would be delighted to help you out. Some instructions and options are listed here: https://t.co/cxzMuceNwR

[MockitoJava @MockitoJava]

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

https://t.co/s9Q3ktwNEG

[MockitoJava @MockitoJava]

@RohanSutar1616 Please file a GitHub issue with exception stacktrace and we can take a look.

[@bricedutheil.bsky.social 🦋 🇪🇺🇺🇦💉 @BriceDutheil]

Someone from the @MockitoJava community created this IntelliJ plugin

It seems to be the very first version : https://t.co/1ZBdwt4kmq

[MockitoJava @MockitoJava]

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: https://t.co/pbGaXU1qlm

[MockitoJava @MockitoJava]

@bukamabish 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.

[Andrei Solntsev @asolntsev]

@MockitoJava Thank you!
We upgraded to Mockito 4.0.0 in several projects - works like a charm (both on Java 11 and Java 17).

[MockitoJava @MockitoJava]

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 https://t.co/pdvkIOk5UM

[MockitoJava @MockitoJava]

@DVyazelenko @rafaelcodes Yes it has been published: https://t.co/Tlaw3X3fLP It can take a while before the Maven Central websites have fully updated and show the new version there as well.

[MockitoJava @MockitoJava]

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 https://t.co/gwSvEpXX0w

[MockitoJava @MockitoJava]

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

[MockitoJava @MockitoJava]

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: https://t.co/B4Jzrd4jqW

[MockitoJava @MockitoJava]

@beatngu1101 @maciejwalkowiak 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.

[MockitoJava @MockitoJava]

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.

[Tim van der Lippe @TimvdLippe]

Mockito is open source and looking for developers working in the Android ecosystem who can help us out with a solution: https://t.co/65hojG6aNL

[MockitoJava @MockitoJava]

For our Android users, we just published version 3.5.2 to Maven Central which should fix the issue with your build (which broke with 3.5.0). Please upgrade and let us know if there are any other issues.

[Andranik Azizbekian @_azizbekian]

@rafaelcodes, after upgrading from mockito 3.4.6 to 3.5.0 test are not able to be run. Is that connected with my setup? Or is there in issue in the release?

[Tim van der Lippe @TimvdLippe]

This is my number one question for the Java ecosystem: how does a (popular) library support modern Java (8+) while not breaking Android support? We have hit this numerous times with Mockito, but surely we cant be the only ones?

[MockitoJava @MockitoJava]

Mockito is now fully ready for the future.

[Oliver Libutzki @OliverLibutzki]

With static mocks you can ensure that the current DateTime is used by your code.

In my opinion use cases for static mocking are rare, but this is an example which shows that it can help you a lot in certain situations.

Thanks
@MockitoJava and @rafaelcodes

[MockitoJava @MockitoJava]

@bhardwaj_rish That's a fair point. Do you mind opening a PR to update the docs with better examples?