@DataJpaTest for repository testing in Spring Boot - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What does @DataJpaTest do in a Spring Boot test?

Consider a Spring Boot test class annotated with @DataJpaTest. What is the main behavior of this annotation during test execution?

A It configures an in-memory database, scans for JPA repositories, and disables full auto-configuration.

B It loads the entire Spring Boot application context including web server and all beans.

C It only loads the web layer components like controllers and filters.

D It disables all database access and mocks repository beans automatically.

💡 Hint

Think about what is needed to test JPA repositories without starting the full app.

@DataJpaTest sets up a minimal Spring context focused on JPA components. It configures an in-memory database by default, scans for repository interfaces, and disables full auto-configuration like web server startup. This makes repository tests fast and isolated.

❓ state_output

intermediate

What is the state of the database after a @DataJpaTest method completes?

In a test class annotated with @DataJpaTest, what happens to the database state after each test method finishes?

A The database is committed and changes are permanently saved after each test.

B The database is rolled back to the initial state before the test method ran.

C The database keeps all changes made during the test method for the next test.

D The database is dropped and recreated only once after all tests finish.

💡 Hint

Think about test isolation and how Spring manages transactions in tests.

By default, @DataJpaTest runs each test method in a transaction that is rolled back after the method completes. This ensures tests do not affect each other and the database state is clean for every test.

📝 Syntax

advanced

Which code snippet correctly injects a repository in a @DataJpaTest class?

Given a repository interface UserRepository, which of the following code snippets correctly injects it into a test class annotated with @DataJpaTest?

A

@DataJpaTest
class UserRepositoryTest {
  @Resource
  private UserRepository userRepository;
}

B

@DataJpaTest
class UserRepositoryTest {
  @Inject
  private UserRepository userRepository;
}

C

@DataJpaTest
class UserRepositoryTest {
  private UserRepository userRepository = new UserRepository();
}

D

@DataJpaTest
class UserRepositoryTest {
  @Autowired
  private UserRepository userRepository;
}

💡 Hint

Which annotation is most commonly used in Spring Boot tests for dependency injection?

@Autowired is the standard Spring annotation to inject beans in test classes. @Inject and @Resource can work but are less common and may require extra configuration. Direct instantiation does not work because Spring manages the bean lifecycle.

🔧 Debug

advanced

Why does this @DataJpaTest fail with NoSuchBeanDefinitionException?

A test class annotated with @DataJpaTest tries to inject MyService which depends on UserRepository. The test fails with NoSuchBeanDefinitionException for MyService. Why?

Spring Boot

@DataJpaTest
class MyServiceTest {
  @Autowired
  private MyService myService;
}

A Because @DataJpaTest only scans repository beans, not service beans like MyService.

B Because MyService is not annotated with @Repository, so Spring ignores it.

C Because @DataJpaTest disables all dependency injection by default.

D Because MyService requires a web environment which @DataJpaTest does not provide.

💡 Hint

Think about what beans @DataJpaTest loads automatically.

@DataJpaTest configures only JPA repository beans and related database infrastructure. It does not load service or controller beans. To test services, you need a different test annotation or manual bean configuration.

🧠 Conceptual

expert

How to include custom configuration beans in a @DataJpaTest?

You want to add a custom bean MyCustomBean to the Spring context during a @DataJpaTest. Which approach correctly adds this bean without loading the full application context?

A Add @ComponentScan(basePackages = "com.example") on the test class.

B Add @SpringBootTest instead of @DataJpaTest to load all beans.

C Use @Import(MyCustomBean.class) on the test class alongside @DataJpaTest.

D Manually instantiate MyCustomBean inside each test method.

💡 Hint

How to add specific beans to a sliced test context?

Using @Import on a @DataJpaTest class adds the specified bean(s) to the test context without loading the full application. @ComponentScan is too broad and @SpringBootTest loads everything, which is slower. Manual instantiation does not register the bean in Spring context.