Mockito dependency setup in JUnit - Build an Automation Script

Verify Mockito dependency setup in a JUnit project

Preconditions (2)

Step 1: Add Mockito dependency to the project's build configuration file (pom.xml for Maven or build.gradle for Gradle)

Step 2: Create a simple test class using JUnit 5

Step 3: Annotate a field with @Mock from Mockito

Step 4: Initialize mocks using MockitoAnnotations.openMocks(this) in a setup method

Step 5: Write a test method that uses the mocked object

Step 6: Run the test

✅ Expected Result: The test runs successfully without errors, indicating Mockito is correctly set up and mocks are working

Automation Requirements - JUnit 5 with Mockito

Assertions Needed:

Test method executes without exceptions

Mocked object is not null

MockitoAnnotations.openMocks(this) initializes mocks properly

Best Practices:

Use @Mock annotation for mock objects

Initialize mocks in a @BeforeEach setup method

Use explicit imports for Mockito and JUnit

Keep test class simple and focused on verifying setup

Automated Solution

JUnit

import static org.junit.jupiter.api.Assertions.assertNotNull;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import org.mockito.Mock;
import org.mockito.MockitoAnnotations;

public class MockitoSetupTest {

    @Mock
    private Runnable mockRunnable;

    @BeforeEach
    void setUp() {
        MockitoAnnotations.openMocks(this);
    }

    @Test
    void testMockIsInitialized() {
        assertNotNull(mockRunnable, "Mock should be initialized");
    }
}

This test class shows how to set up Mockito in a JUnit 5 project.

We import necessary classes from JUnit and Mockito.

The @Mock annotation marks mockRunnable as a mock object.

In the @BeforeEach method setUp(), we call MockitoAnnotations.openMocks(this) to initialize all mocks annotated with @Mock.

The test method testMockIsInitialized() asserts that the mock object is not null, confirming Mockito is set up correctly.

This simple test ensures the dependency is correctly added and mocks work as expected.

Common Mistakes - 4 Pitfalls

{'mistake': 'Not adding Mockito dependency in the build file', 'why_bad': "Without the dependency, Mockito classes won't be found and tests will fail to compile.", 'correct_approach': 'Add the correct Mockito dependency in pom.xml or build.gradle before writing tests.'}

Forgetting to initialize mocks with MockitoAnnotations.openMocks(this)

{'mistake': 'Using @Mock without importing it from Mockito', 'why_bad': "The annotation won't be recognized and tests won't compile.", 'correct_approach': 'Import org.mockito.Mock explicitly.'}

Mixing JUnit 4 and JUnit 5 annotations

Bonus Challenge

Add a test that mocks a List and verifies a method call

Show Hint