@DataJpaTest for repository testing in Spring Boot - Step-by-Step Execution

Concept Flow - @DataJpaTest for repository testing

Start Test Class

↓

@DataJpaTest Annotation

↓

Spring Boot Loads In-Memory DB

↓

Inject Repository Bean

↓

Run Repository Methods

↓

Verify Results

↓

Test Ends

The test class annotated with @DataJpaTest loads an in-memory database and injects the repository to run and verify database operations.

Execution Sample

Spring Boot

import org.springframework.boot.test.autoconfigure.orm.jpa.DataJpaTest;
import org.springframework.beans.factory.annotation.Autowired;
@DataJpaTest
class UserRepositoryTest {
  @Autowired
  UserRepository repo;
  // test methods here
}

This code sets up a test class that uses @DataJpaTest to test UserRepository with an in-memory database.

Execution Table

Step	Action	Spring Boot Behavior	Repository State	Test Output
1	Test class starts	Spring Boot prepares test context	Repository bean not yet injected	No output
2	@DataJpaTest triggers in-memory DB setup	H2 database starts	Repository bean created and injected	No output
3	Repository method called (e.g., save)	Transaction starts	Entity saved in in-memory DB	Entity saved successfully
4	Repository method called (e.g., findById)	Query executed on in-memory DB	Entity retrieved	Entity returned
5	Assertions run	Test framework checks results	Repository state unchanged	Pass or Fail based on assertions
6	Test ends	Transaction rolls back automatically	In-memory DB cleared	Test context closed

💡 Test ends after assertions; in-memory DB is cleared to keep tests isolated.

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
Repository Bean	null	Injected instance	Injected instance	Injected instance
In-Memory DB	empty	Contains saved entity	Contains saved entity	empty (rolled back)
Entity	null	Saved entity instance	Retrieved entity instance	null (rolled back)

Key Moments - 3 Insights

Why does the database get cleared after the test?

Because @DataJpaTest runs each test in a transaction that rolls back at the end, ensuring no data persists between tests (see Step 6 in execution_table).

Is the real database used during @DataJpaTest?

No, @DataJpaTest uses an in-memory database like H2 by default to keep tests fast and isolated (see Step 2 in execution_table).

How does the repository get available in the test?

Spring Boot injects the repository bean automatically into the test class because of @DataJpaTest and @Autowired (see Step 2 and 3 in execution_table).

Visual Quiz - 3 Questions

Look at the execution table, what happens at Step 3?

A Repository method saves an entity in the in-memory DB

B Test ends and database is cleared

C Repository bean is injected

D Assertions are run

💡 Hint

Check the 'Action' and 'Repository State' columns at Step 3 in the execution_table.

At which step does Spring Boot start the in-memory database?

A Step 1

B Step 2

C Step 4

D Step 6

💡 Hint

Look for 'H2 database starts' in the 'Spring Boot Behavior' column.

If the transaction did not roll back after the test, what would change in variable_tracker?

A In-Memory DB would remain empty

B Repository Bean would be null

C In-Memory DB would still contain saved entities after test

D Entity variable would be null at start

💡 Hint

Refer to the 'In-Memory DB' row in variable_tracker and Step 6 in execution_table.

Concept Snapshot

@DataJpaTest sets up an in-memory database and injects repository beans for testing.
Each test runs in a transaction that rolls back after completion.
This keeps tests isolated and fast without affecting real data.
Use @Autowired to get repository instances in your test class.
Run repository methods and assert results as usual.
The in-memory DB resets after each test automatically.

Full Transcript

When you write a test class with @DataJpaTest, Spring Boot starts an in-memory database like H2 and injects your repository bean. You can then call repository methods such as save or findById. Each test runs inside a transaction that automatically rolls back when the test finishes, so no data stays in the database. This keeps tests clean and isolated. The repository bean is available because Spring Boot creates and injects it for you. After running your assertions, the test ends and the in-memory database clears. This process helps you test your database code quickly without touching your real database.