25.12. Mocking in Unit Tests

Sometimes, components depend on external systems (DB, APIs). Mocking replaces those with dummy implementations.

Mocking is a technique used in unit testing when a component of the software interacts with an external system, such as a database or an API. Instead of making actual calls to these external systems, which may be slow, unreliable, or cause side effects, developers create 'mock' versions of those components. These mock components simulate the behavior of the real components but with controlled responses. This means developers can run their tests in isolation without worrying about the actual state of external systems.

Think of mocking like using a practice car in a driving school. The driving school car represents the real car (the external system) that you would eventually drive on the road. However, in a safe environment, you learn how to control the car without putting yourself in danger. Similarly, mocking allows developers to practice their code without dependency on real external services.

Mockito Example

@Mock
UserRepository userRepository;
@Test
void testFindUser() {
    when(userRepository.findById(1)).thenReturn(new User(1, "Alice"));
    assertEquals("Alice", userRepository.findById(1).getName());
}

In this example, we see how to use Mockito, a popular mocking framework in Java. We start by declaring a mock object for the UserRepository, which is assumed to be a component that interacts with a database to find user information. The @Mock annotation indicates that this is a mock object. In the test method testFindUser, we tell the mock to return a predefined User object when a specific method, findById, is called with the value 1. The assertEquals statement checks if the name of the user obtained from the mocked repository matches the expected value, which is 'Alice'. This allows us to test the findById method's handling of retrieved data without needing an actual database.

Imagine a teacher preparing a class where students are learning about famous historical figures. Instead of requiring the students to research every figure directly, the teacher may provide a set of flashcards with prepared information. When a student picks a card and reads aloud about a figure, the teacher can verify if their knowledge (the test) is correct. By using the flashcards as mock information, the teacher ensures that the learning environment remains structured and controlled, much like how mocking lets developers focus on testing their code without interference from external components.

--