Argument captors in JUnit - Test Execution Trace

Test Overview

This test verifies that a method correctly calls a dependency with the expected argument by capturing the argument passed to a mocked method using an argument captor.

Test Code - JUnit + Mockito

JUnit

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

class UserServiceTest {

    interface UserRepository {
        void saveUser(String username);
    }

    static class UserService {
        private final UserRepository repo;

        UserService(UserRepository repo) {
            this.repo = repo;
        }

        void registerUser(String username) {
            // Some logic before saving
            repo.saveUser(username);
        }
    }

    @Test
    void testRegisterUserCapturesArgument() {
        UserRepository mockRepo = mock(UserRepository.class);
        UserService service = new UserService(mockRepo);

        service.registerUser("alice");

        ArgumentCaptor<String> captor = ArgumentCaptor.forClass(String.class);
        verify(mockRepo).saveUser(captor.capture());

        String capturedArg = captor.getValue();
        assertEquals("alice", capturedArg);
    }
}

Execution Trace - 8 Steps

Step	Action	System State	Assertion	Result
1	Test starts	JUnit test runner initializes the test class UserServiceTest	—	PASS
2	Creates a mock UserRepository using Mockito	mockRepo is a mock object that records interactions	—	PASS
3	Creates UserService instance with mockRepo injected	UserService instance ready to use mockRepo	—	PASS
4	Calls registerUser("alice") on UserService	Inside registerUser, calls mockRepo.saveUser("alice")	—	PASS
5	Creates ArgumentCaptor for String class	ArgumentCaptor ready to capture String arguments	—	PASS
6	Verifies mockRepo.saveUser was called and captures the argument	Captured argument is stored inside captor	Verify that saveUser was called once with any String argument	PASS
7	Retrieves captured argument and asserts it equals "alice"	Captured argument is "alice"	assertEquals("alice", capturedArg)	PASS
8	Test ends successfully	Test passed with all assertions met	—	PASS

Failure Scenario

Failing Condition: The method saveUser was not called or called with a different argument than expected

Execution Trace Quiz - 3 Questions

What does the ArgumentCaptor capture in this test?

A The number of times saveUser was called

B The return value of saveUser method

C The argument passed to the mockRepo.saveUser method

D The exception thrown by saveUser

Key Result

Using argument captors helps verify that methods are called with the correct data, improving test accuracy beyond just checking if a method was called.

Practice

1. What is the main purpose of using an ArgumentCaptor in JUnit tests with Mockito?

easy

A. To capture and inspect the arguments passed to a mocked method

B. To create a mock object for testing

C. To verify the number of times a method was called

D. To stub the return value of a method

Solution

1. Step 1: Understand ArgumentCaptor role

   An ArgumentCaptor is used to catch the actual arguments passed to a mock's method during test execution.

2. Step 2: Differentiate from other Mockito features

   Unlike mocks or verify count, ArgumentCaptor focuses on capturing and inspecting method arguments.

3. Final Answer:

   To capture and inspect the arguments passed to a mocked method -> Option A

4. Quick Check:

   ArgumentCaptor captures arguments [OK]

Hint: ArgumentCaptor catches method inputs for checking [OK]

Common Mistakes:

• Confusing ArgumentCaptor with mock creation
• Thinking it counts method calls
• Assuming it stubs return values

2. Which of the following is the correct way to declare an ArgumentCaptor for a String argument in JUnit with Mockito?

easy

A. ArgumentCaptor<String> captor = ArgumentCaptor.forClass(String.class);

B. ArgumentCaptor captor = new ArgumentCaptor<String>();

C. ArgumentCaptor<String> captor = new ArgumentCaptor<>();

D. ArgumentCaptor<String> captor = ArgumentCaptor.capture(String.class);

Solution

1. Step 1: Recall ArgumentCaptor creation syntax

   The correct way is to use the static method forClass() with the class type.

2. Step 2: Check each option for syntax correctness

   ArgumentCaptor<String> captor = ArgumentCaptor.forClass(String.class); uses ArgumentCaptor.forClass(String.class), which is correct. Options B and C incorrectly use constructors, which are not public. ArgumentCaptor<String> captor = ArgumentCaptor.capture(String.class); uses a non-existent method capture() for creation.

3. Final Answer:

   ArgumentCaptor<String> captor = ArgumentCaptor.forClass(String.class); -> Option A

4. Quick Check:

   Use forClass() to create captor [OK]

Hint: Use ArgumentCaptor.forClass(Type.class) to declare captor [OK]

Common Mistakes:

• Trying to instantiate ArgumentCaptor with new
• Using non-existent capture() method
• Omitting the class type in forClass()

3. Given the following code snippet, what will be the captured argument value?

List<String> list = mock(List.class);
ArgumentCaptor<String> captor = ArgumentCaptor.forClass(String.class);
list.add("hello");
verify(list).add(captor.capture());
String captured = captor.getValue();

medium

A. null

B. "hello"

C. "captor"

D. Throws an exception

Solution

1. Step 1: Understand the mock and method call

   The mock list has add("hello") called, so "hello" is passed as argument.

2. Step 2: Verify and capture argument

   The verify(list).add(captor.capture()) captures the argument passed to add(), which is "hello".

3. Final Answer:

   "hello" -> Option B

4. Quick Check:

   Captured argument matches method call input [OK]

Hint: Captured value equals argument passed to mock method [OK]

Common Mistakes:

• Assuming captor captures method name
• Expecting null if not stubbed
• Thinking it throws exception without stubbing

4. Identify the error in the following test code using ArgumentCaptor:

ArgumentCaptor<Integer> captor = ArgumentCaptor.forClass(Integer.class);
verify(mockedList).add(captor.capture());
mockedList.add(5);
Integer value = captor.getValue();

medium

A. ArgumentCaptor should be declared after method call

B. No error, code is correct

C. Captor must be reset before use

D. The verify call is before the actual method call

Solution

1. Step 1: Analyze order of method call and verify

   The verify() call must come after the actual method call to check interactions.

2. Step 2: Identify the mistake

   Here, verify() is called before mockedList.add(5), so no interaction is recorded yet.

3. Final Answer:

   The verify call is before the actual method call -> Option D

4. Quick Check:

   Verify after method call [OK]

Hint: Always call verify() after the method under test [OK]

Common Mistakes:

• Calling verify before method invocation
• Assuming captor resets automatically
• Declaring captor after verify

5. You want to verify that a mocked service method was called twice with different String arguments, and capture both arguments for assertions. Which approach correctly uses ArgumentCaptor to achieve this?

hard

A. Use ArgumentCaptor only once; it cannot capture multiple calls

B. Create two separate ArgumentCaptors and verify each call separately

C. Use a single ArgumentCaptor and call getAllValues() after verifying two calls

D. Capture arguments by stubbing the method instead of verify

Solution

1. Step 1: Understand multiple call verification with ArgumentCaptor

   A single ArgumentCaptor can capture all arguments from multiple calls using getAllValues().

2. Step 2: Evaluate options for capturing multiple arguments

   Use a single ArgumentCaptor and call getAllValues() after verifying two calls correctly uses one captor and retrieves all captured arguments. Create two separate ArgumentCaptors and verify each call separately is unnecessary and verbose. Use ArgumentCaptor only once; it cannot capture multiple calls is false; captor supports multiple captures. Capture arguments by stubbing the method instead of verify is incorrect because stubbing does not capture arguments.

3. Final Answer:

   Use a single ArgumentCaptor and call getAllValues() after verifying two calls -> Option C

4. Quick Check:

   Single captor + getAllValues() captures multiple calls [OK]

Hint: Use getAllValues() on one captor for multiple calls [OK]

Common Mistakes:

• Creating multiple captors unnecessarily
• Thinking captor captures only one call
• Trying to capture arguments via stubbing