Why mocking isolates units under test in JUnit - Test Execution Impact

Test Overview

This test checks how mocking helps isolate a unit by replacing its dependencies with mocks. It verifies that the unit behaves correctly when its dependency returns a controlled value.

Test Code - JUnit 5 with Mockito

JUnit

import static org.mockito.Mockito.*;
import static org.junit.jupiter.api.Assertions.*;
import org.junit.jupiter.api.Test;

class Service {
    private final Dependency dependency;
    Service(Dependency dependency) {
        this.dependency = dependency;
    }
    String serve() {
        return "Service calls " + dependency.getData();
    }
}

interface Dependency {
    String getData();
}

public class ServiceTest {
    @Test
    void testServeWithMockedDependency() {
        Dependency mockDep = mock(Dependency.class);
        when(mockDep.getData()).thenReturn("mocked data");

        Service service = new Service(mockDep);
        String result = service.serve();

        assertEquals("Service calls mocked data", result);
    }
}

Execution Trace - 6 Steps

Step	Action	System State	Assertion	Result
1	Test starts	JUnit test runner initialized	-	PASS
2	Mockito creates a mock object for Dependency interface	Mock object ready to simulate Dependency	-	PASS
3	Stub getData() method of mock to return 'mocked data'	Mock configured to return controlled value	-	PASS
4	Create Service instance with mocked Dependency	Service uses mock instead of real Dependency	-	PASS
5	Call serve() method on Service instance	Service calls mock's getData() method	Check that serve() returns 'Service calls mocked data'	PASS
6	Test ends	Test completed successfully	-	PASS

Failure Scenario

Failing Condition: Mock not configured correctly or returns unexpected value

Execution Trace Quiz - 3 Questions

What is the main purpose of mocking in this test?

A To test the real Dependency implementation

B To replace the real dependency with a controlled fake

C To speed up the Service method

D To avoid writing assertions

Key Result

Mocking isolates the unit under test by replacing real dependencies with controlled mocks, allowing focused testing of the unit's behavior without side effects or external dependencies.