Question 1

How to mock static methods in Mockito?

Accepted Answer

Use the mockito-inline dependency introduced in version 5, which allows mocking static methods via Mockito.mockStatic(), but requires additional setup in your build configuration. This is a change from earlier versions where it was more limited.

Question 2

Mockito vs EasyMock which is better?

Accepted Answer

Mockito is generally preferred for its cleaner API and better integration with modern Java frameworks, while EasyMock is older and more verbose. Mockito's fluent syntax and annotation support make tests more readable and maintainable in most cases.

Question 3

How to use Mockito with JUnit 5?

Accepted Answer

Add the Mockito extension for JUnit 5, such as @ExtendWith(MockitoExtension.class), to enable annotation-based mocking without manual setup. This integrates seamlessly with JUnit 5's extension model for streamlined testing.

Question 4

What changed from Mockito 4 to 5?

Accepted Answer

Mockito 5 switched the default mockmaker to mockito-inline for better static mocking and now requires Java 11 instead of Java 8. It also removed some deprecated APIs, so upgrading may require code adjustments for compatibility.

Question 5

Can Mockito mock final classes?

Accepted Answer

Yes, but only with the mockito-inline mockmaker enabled, which is the default in version 5. Earlier versions required explicit configuration, and performance might be slightly impacted compared to non-final mocks.

Question 6

How to verify method calls in Mockito?

Accepted Answer

Use Mockito.verify() with the mock object and specify the method call, optionally with argument matchers or times() for call counts. This allows precise interaction testing to ensure dependencies behave as expected in tests.

Mockito

What is Mockito?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions