@Mock annotation in JUnit - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the @Mock annotation in JUnit testing?

The @Mock annotation is used to create mock objects. These are fake versions of real objects that simulate behavior for testing without using the actual implementation.

intermediate

How do you initialize mocks annotated with @Mock in a JUnit 5 test class?

You initialize mocks by calling MockitoAnnotations.openMocks(this) in a setup method annotated with @BeforeEach. This prepares the mock objects before each test runs.

intermediate

What is the difference between a mock and a spy in testing?

A mock simulates an object and does not call real methods unless specified. A spy wraps a real object and calls real methods unless stubbed to do otherwise.

beginner

Can you use @Mock without a mocking framework like Mockito?

No, @Mock is part of Mockito and requires it to create mock objects. Without Mockito or a similar framework, @Mock has no effect.

beginner

Why is mocking useful in unit testing?

Mocking helps isolate the unit being tested by replacing dependencies with controlled fake objects. This makes tests faster, more reliable, and focused on the unit's behavior.

What does the @Mock annotation do in a JUnit test?

A Marks a test method to be ignored

B Runs the actual method implementation

C Initializes the test class

D Creates a fake object to simulate behavior

@Mock creates a fake object to simulate behavior for testing.

How do you activate mocks annotated with @Mock in JUnit 5?

A Use <code>@RunWith(MockitoJUnitRunner.class)</code>

B Call <code>MockitoAnnotations.openMocks(this)</code> in <code>@BeforeEach</code>

C Mocks are active by default

D Call <code>initMocks()</code> in <code>@AfterEach</code>

In JUnit 5, you activate mocks by calling MockitoAnnotations.openMocks(this) in a setup method.

Which framework provides the @Mock annotation?

A TestNG

B JUnit

C Mockito

D Selenium

@Mock is provided by the Mockito framework.

What is a key benefit of using mocks in unit tests?

A Isolates the unit by replacing dependencies

B Runs tests slower

C Requires real database connections

D Makes tests dependent on network

Mocks isolate the unit by replacing dependencies with controlled fake objects.

Which statement about mocks is true?

A Mocks simulate objects without calling real methods by default

B Mocks always call real methods

C Mocks cannot be used in JUnit tests

D Mocks are used to style UI components

Mocks simulate objects and do not call real methods unless specified.

Explain how the @Mock annotation works and why it is useful in unit testing.

Think about replacing real parts with fake ones to test only what you want.

Describe the steps to use @Mock in a JUnit 5 test class.

Initialization is key before running tests.

Practice

1. What is the main purpose of the @Mock annotation in JUnit testing?

easy

A. To create fake objects that simulate real dependencies for testing

B. To run tests in parallel threads

C. To generate test reports automatically

D. To connect to a real database during tests

Solution

1. Step 1: Understand the role of @Mock

   The @Mock annotation is used to create fake objects that imitate real dependencies in tests.

2. Step 2: Identify the purpose in testing context

   This helps isolate the code being tested from external systems or complex objects.

3. Final Answer:

   To create fake objects that simulate real dependencies for testing -> Option A

4. Quick Check:

   @Mock creates fake objects [OK]

Hint: Mocks create fake objects to isolate tests [OK]

Common Mistakes:

• Thinking @Mock runs tests in parallel
• Confusing @Mock with test report generation
• Assuming @Mock connects to real databases

2. Which of the following is the correct way to declare a mock object using @Mock in a JUnit 5 test class?

easy

A. @Mock private MyService service;

B. @Mock MyService service = new MyService();

C. @Mock public void service();

D. @Mock MyService service = null;

Solution

1. Step 1: Check correct syntax for @Mock field declaration

   The mock object should be declared as a private field with the @Mock annotation and no initialization.

2. Step 2: Identify the correct option

   @Mock private MyService service; correctly declares: @Mock private MyService service; without initializing it.

3. Final Answer:

   @Mock private MyService service; -> Option A

4. Quick Check:

   Declare mock as private field without initialization [OK]

Hint: Declare mocks as private fields without new keyword [OK]

Common Mistakes:

• Initializing mock objects manually
• Using @Mock on methods instead of fields
• Declaring mocks as public or with invalid syntax

3. Given the following JUnit 5 test code snippet, what will be the output of service.getData() when called inside the test?

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

class MyServiceTest {
  @Mock
  MyService service;

  @Test
  void testGetData() {
    MockitoAnnotations.openMocks(this);
    when(service.getData()).thenReturn("mocked data");
    System.out.println(service.getData());
  }
}

medium

A. Original data from MyService

B. null

C. Throws NullPointerException

D. mocked data

Solution

1. Step 1: Understand mock initialization

   The call to MockitoAnnotations.openMocks(this) initializes the @Mock annotated fields.

2. Step 2: Analyze the stubbed method behavior

   The line when(service.getData()).thenReturn("mocked data") sets the mock to return "mocked data" when getData() is called.

3. Final Answer:

   mocked data -> Option D

4. Quick Check:

   Stubbed mock method returns set value [OK]

Hint: Initialize mocks and stub methods to control output [OK]

Common Mistakes:

• Forgetting to initialize mocks before use
• Expecting real method output instead of stubbed
• Confusing null return with stubbed return

4. Identify the error in the following JUnit 5 test code using @Mock:

import org.junit.jupiter.api.Test;
import org.mockito.Mock;

class UserServiceTest {
  @Mock
  UserRepository repo;

  @Test
  void testFindUser() {
    when(repo.findUserById(1)).thenReturn(new User(1, "Alice"));
    UserService service = new UserService(repo);
    User user = service.findUser(1);
    assertEquals("Alice", user.getName());
  }
}

medium

A. The test method is missing the @Mock annotation

B. The when method is used incorrectly

C. Mocks are not initialized before use

D. UserService constructor cannot accept mocks

Solution

1. Step 1: Check mock initialization

   The code declares @Mock UserRepository repo; but never initializes mocks with MockitoAnnotations.openMocks(this) or similar.

2. Step 2: Understand consequence of missing initialization

   Without initialization, repo is null, so calling when(repo.findUserById(1)) causes a NullPointerException.

3. Final Answer:

   Mocks are not initialized before use -> Option C

4. Quick Check:

   Always initialize mocks before using them [OK]

Hint: Always initialize mocks before calling methods on them [OK]

Common Mistakes:

• Forgetting MockitoAnnotations.openMocks(this)
• Assuming @Mock auto-initializes mocks
• Misusing when() without initialized mocks

5. You want to test a service method that depends on two different collaborators. You use @Mock to create fake objects for both. Which of the following is the best practice to ensure your mocks work correctly in the test?

hard

A. Declare mocks as local variables inside test methods

B. Initialize mocks with MockitoAnnotations.openMocks(this) in a setup method

C. Use real instances instead of mocks for better accuracy

D. Manually instantiate mocks with new keyword

Solution

1. Step 1: Understand mock initialization best practice

   Mocks annotated with @Mock must be initialized before use, typically by calling MockitoAnnotations.openMocks(this) in a setup method.

2. Step 2: Evaluate other options

   Manually creating mocks with new is incorrect; real instances break isolation; local variables lose scope and initialization benefits.

3. Final Answer:

   Initialize mocks with MockitoAnnotations.openMocks(this) in a setup method -> Option B

4. Quick Check:

   Initialize mocks in setup for reliable tests [OK]

Hint: Initialize all @Mock fields in setup method [OK]

Common Mistakes:

• Creating mocks manually with new keyword
• Using real objects instead of mocks
• Declaring mocks inside test methods without initialization