Why advanced mocking handles complex dependencies in JUnit - Automation Benefits in Action

Verify service method behavior with complex dependencies using advanced mocking

Preconditions (2)

Step 1: Mock the two dependent services using Mockito

Step 2: Stub methods of the dependent services to return specific values

Step 3: Inject mocks into the service under test

Step 4: Call the service method that uses both dependencies

Step 5: Verify the returned result matches expected output based on mocked dependencies

Step 6: Verify that dependent services methods were called with correct arguments

✅ Expected Result: The service method returns the correct result based on mocked dependencies and all interactions with dependencies are verified

Automation Requirements - JUnit 5 with Mockito

Assertions Needed:

Assert the service method returns expected value

Verify dependent service methods are called with expected arguments

Best Practices:

Use @ExtendWith(MockitoExtension.class) for Mockito integration

Use @Mock and @InjectMocks annotations for cleaner setup

Use when().thenReturn() for stubbing

Use verify() to check interactions

Avoid mocking concrete classes unless necessary

Automated Solution

JUnit

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

import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.extension.ExtendWith;
import org.mockito.InjectMocks;
import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;

@ExtendWith(MockitoExtension.class)
class ComplexServiceTest {

    @Mock
    DependencyServiceA serviceA;

    @Mock
    DependencyServiceB serviceB;

    @InjectMocks
    ComplexService complexService;

    @Test
    void testComplexServiceMethod() {
        // Arrange: stub dependent services
        when(serviceA.getData()).thenReturn("dataA");
        when(serviceB.process("dataA")).thenReturn("processedDataB");

        // Act: call method under test
        String result = complexService.combineData();

        // Assert: verify result and interactions
        assertEquals("Result: processedDataB", result);
        verify(serviceA).getData();
        verify(serviceB).process("dataA");
    }
}

// Supporting classes for context
class ComplexService {
    private final DependencyServiceA serviceA;
    private final DependencyServiceB serviceB;

    public ComplexService(DependencyServiceA serviceA, DependencyServiceB serviceB) {
        this.serviceA = serviceA;
        this.serviceB = serviceB;
    }

    public String combineData() {
        String data = serviceA.getData();
        String processed = serviceB.process(data);
        return "Result: " + processed;
    }
}

interface DependencyServiceA {
    String getData();
}

interface DependencyServiceB {
    String process(String input);
}

This test uses Mockito with JUnit 5 to handle complex dependencies.

We use @Mock to create mocks for the two dependent services. @InjectMocks injects these mocks into the service under test.

We stub the dependent services' methods to return controlled values using when().thenReturn(). This simulates complex interactions without needing real implementations.

The test calls the service method and asserts the returned value matches the expected result based on the mocks.

Finally, verify() checks that the dependent services were called correctly, ensuring the service interacts properly with its dependencies.

This approach isolates the service logic and handles complex dependencies cleanly and reliably.

Common Mistakes - 4 Pitfalls

Not using @ExtendWith(MockitoExtension.class) causing mocks not to initialize

Mocking concrete classes instead of interfaces

Not verifying interactions with mocks

Hardcoding return values without considering input arguments

Bonus Challenge

Now add data-driven testing with 3 different input scenarios for the dependent services

Show Hint

Practice

1. Why do we use advanced mocking in JUnit tests when dealing with complex dependencies?

easy

A. To automatically generate user interfaces

B. To isolate the code under test and control the behavior of its dependencies

C. To avoid writing any test cases

D. To make the code run faster in production

Solution

1. Step 1: Understand the purpose of mocking

   Mocking replaces real dependencies with fake ones to isolate the code being tested.

2. Step 2: Recognize the benefit of advanced mocking

   Advanced mocking allows control over complex dependencies, making tests reliable and focused.

3. Final Answer:

   To isolate the code under test and control the behavior of its dependencies -> Option B

4. Quick Check:

   Mocking isolates dependencies [OK]

Hint: Mocking isolates dependencies to test code alone [OK]

Common Mistakes:

• Thinking mocking speeds up production code
• Believing mocking removes the need for tests
• Confusing mocking with UI generation

2. Which of the following is the correct syntax to create a mock object using Mockito in a JUnit test?

easy

A. MyClass mock = Mockito.mock(MyClass.class);

B. MyClass mock = new MyClass();

C. MyClass mock = mockito.create(MyClass);

D. MyClass mock = Mockito.createMock(MyClass);

Solution

1. Step 1: Recall Mockito mock creation syntax

   Mockito uses the static method mock(Class) to create mock objects.

2. Step 2: Verify the correct syntax

   The correct syntax is: MyClass mock = Mockito.mock(MyClass.class);

3. Final Answer:

   MyClass mock = Mockito.mock(MyClass.class); -> Option A

4. Quick Check:

   Mockito.mock(Class) creates mocks [OK]

Hint: Use Mockito.mock(Class.class) to create mocks [OK]

Common Mistakes:

• Using new keyword instead of Mockito.mock
• Calling non-existent Mockito methods
• Incorrect class reference syntax

3. Given the following JUnit test code using Mockito:

@ExtendWith(MockitoExtension.class)
class ServiceTest {
  @Mock
  Repository repo;

  @InjectMocks
  Service service;

  @Test
  void testGetData() {
    when(repo.fetch()).thenReturn("data");
    String result = service.getData();
    assertEquals("data", result);
  }
}

What will be the test result if repo.fetch() is called inside service.getData()?

medium

A. Test fails because repo.fetch() returns null

B. Test fails due to syntax error in mocking

C. Test throws NullPointerException due to uninitialized repo

D. Test passes because repo.fetch() returns mocked "data"

Solution

1. Step 1: Understand Mockito annotations usage

   @Mock creates a mock for Repository, and @InjectMocks injects it into Service.

2. Step 2: Analyze the when-thenReturn setup

   Calling repo.fetch() returns "data" as stubbed, so service.getData() returns "data".

3. Final Answer:

   Test passes because repo.fetch() returns mocked "data" -> Option D

4. Quick Check:

   Mock returns stubbed value [OK]

Hint: Stub methods with when().thenReturn() to control outputs [OK]

Common Mistakes:

• Assuming mocks return null by default
• Forgetting to initialize mocks with @ExtendWith or MockitoAnnotations
• Confusing mock injection with real object creation

4. Consider this JUnit test snippet using Mockito:

@ExtendWith(MockitoExtension.class)
class TestClass {
  @Mock
  Database db;

  @Test
  void testQuery() {
    when(db.query("SELECT * FROM users")).thenReturn(null);
    String result = db.query("SELECT * FROM users");
    assertNotNull(result);
  }
}

What is the problem with this test?

medium

A. The assertion will fail because the mock returns null

B. The syntax of when() is incorrect

C. The mock object db is not created properly

D. The test will pass because null is acceptable

Solution

1. Step 1: Analyze the stubbed return value

   The mock is set to return null for the query method call.

2. Step 2: Check the assertion logic

   The test asserts that the result is not null, but the stub returns null, so assertion fails.

3. Final Answer:

   The assertion will fail because the mock returns null -> Option A

4. Quick Check:

   Assertion contradicts stubbed null [OK]

Hint: Match stubbed return values with assertions [OK]

Common Mistakes:

• Ignoring that stub returns null
• Assuming syntax error without checking code
• Believing test passes with failing assertions

5. You have a service class that depends on two complex external APIs. You want to write a JUnit test that verifies your service logic without calling these APIs. Which advanced mocking approach best handles this scenario?

hard

A. Manually create fake API responses inside the service code

B. Write integration tests that call the real APIs directly

C. Use Mockito to create mocks for both API clients and inject them into the service

D. Skip testing the service since APIs are complex

Solution

1. Step 1: Identify the need to isolate service from external APIs

   Testing should avoid calling real APIs to keep tests fast and reliable.

2. Step 2: Choose advanced mocking to simulate API behavior

   Mockito mocks for API clients allow controlling responses and injecting them into the service.

3. Final Answer:

   Use Mockito to create mocks for both API clients and inject them into the service -> Option C

4. Quick Check:

   Mock external APIs to isolate service [OK]

Hint: Mock external dependencies to isolate service logic [OK]

Common Mistakes:

• Testing with real APIs causing slow or flaky tests
• Hardcoding fake responses inside service code
• Avoiding tests due to complexity