@MockBean for mocking dependencies in Spring Boot - Step-by-Step Execution

Concept Flow - @MockBean for mocking dependencies

Start Test

↓

Spring Context Loads

↓

@MockBean Creates Mock

↓

Inject Mock into Context

↓

Test Runs Using Mock

↓

Verify Behavior or Output

↓

Test Ends

The test starts by loading Spring context, then @MockBean creates a mock object and injects it into the context, replacing the real bean. The test runs using this mock, allowing controlled behavior and verification.

Execution Sample

Spring Boot

@MockBean
private UserService userService;

@Test
void testGetUser() {
  when(userService.getUser()).thenReturn(new User("Alice"));
  String name = userService.getUser().getName();
  assertEquals("Alice", name);
}

This test mocks UserService, sets a return value for getUser(), calls it, and checks the returned name.

Execution Table

Step	Action	Mock State	Method Called	Return Value	Test Assertion
1	@MockBean creates mock UserService	UserService mock created	none	none	none
2	when(userService.getUser()).thenReturn(new User("Alice"))	Stub set for getUser()	none	none	none
3	Call userService.getUser()	Stub active	getUser()	User("Alice")	none
4	Call getName() on returned User	Stub active	getName()	"Alice"	none
5	assertEquals("Alice", name)	Stub active	none	none	Pass
6	Test ends	Mock cleaned	none	none	Test success

💡 Test ends after assertion passes using mocked UserService

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
userService	null	mock object	mock object	mock object	mock object
name	null	null	User("Alice")	"Alice"	"Alice"

Key Moments - 2 Insights

Why does userService.getUser() return a User object even though userService is a mock?

Because at step 2 in the execution_table, we set a stub with when(...).thenReturn(...), telling the mock what to return when getUser() is called.

Does @MockBean replace the real bean in the Spring context?

Yes, as shown in the concept_flow, @MockBean creates a mock and injects it into the Spring context, replacing the real bean for the test.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What does userService.getUser() return?

A User("Alice") from the mock

B A real User from the database

C null

D An exception

💡 Hint

Check the 'Return Value' column at step 3 in the execution_table.

At which step is the stub for getUser() set on the mock?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Look for when(...).thenReturn(...) in the 'Action' column of the execution_table.

If we remove @MockBean, what would happen to the test?

A Test would still use the mock

B Test would fail to start Spring context

C Test would use the real UserService bean

D Test would pass without any changes

💡 Hint

Refer to the concept_flow about how @MockBean replaces the real bean in the context.

Concept Snapshot

@MockBean creates a mock of a Spring bean and injects it into the test context.
Use when(...).thenReturn(...) to define mock behavior.
The mock replaces the real bean during tests.
This allows isolated testing without real dependencies.
Assertions verify expected mock interactions or outputs.

Full Transcript

In Spring Boot tests, @MockBean creates a mock object of a bean and injects it into the Spring context, replacing the real bean. This lets tests control and verify the behavior of dependencies. The test sets up the mock's behavior using when(...).thenReturn(...). When the test calls methods on the mock, it returns the stubbed values. Assertions check these returned values to confirm correct behavior. This approach isolates the unit under test from real dependencies, making tests faster and more reliable.