Spring Data JPA Repository Testing | Java Fresher Interview

Direct Answer

Use @DataJpaTest to test entity mappings, repository queries, and persistence behavior in a JPA-focused Spring context. Tests are transactional and normally roll back, and Boot commonly replaces the configured data source with an available embedded database. That replacement is not guaranteed to behave like production; use the production database through Testcontainers and disable replacement when dialect-specific behavior matters.

Code Example

@DataJpaTest
class OrderRepositoryTest {
    @Autowired
    private OrderRepository orderRepository;
    
    @Autowired
    private TestEntityManager entityManager;
    
    @Test
    void shouldFindOrdersByCustomerEmail() {
        var customer = new Customer(null, "alice@example.com");
        entityManager.persist(customer);
        
        var order1 = new Order(null, "Laptop", 1500.00, customer);
        var order2 = new Order(null, "Mouse", 25.00, customer);
        entityManager.persistAndFlush(order1);
        entityManager.persistAndFlush(order2);
        
        var orders = orderRepository.findByCustomerEmail("alice@example.com");
        
        assertEquals(2, orders.size());
        assertTrue(orders.stream().anyMatch(o -> o.getItem().equals("Laptop")));
    }
}

Common Mistakes & Pitfalls

• Assuming H2 is automatic: Boot needs an embedded database dependency or an explicitly configured data source.
• Treating database products as interchangeable: H2 success does not prove PostgreSQL or MySQL behavior.
• Testing only the persistence cache: use flush() and clear() when a real database round trip matters.
• Expecting every side effect to roll back: independent transactions and external threads are outside the test transaction.
• Mocking the repository: that tests service logic, not JPA mappings or queries.