@DirtiesContext Explained

Direct Answer

@DirtiesContext marks a test ApplicationContext as dirty so the TestContext framework removes it from the cache and closes it. Depending on the configured class or method mode, this can happen before or after a test. Use it when a test changes context-level state that cannot be reset safely, because a later test may then have to build a new context.

Code Example

@SpringBootTest
@DirtiesContext // rebuild the context after this class — genuinely needed here
class ConnectionPoolShutdownTest {
    @Autowired DataSource dataSource;

    @Test
    void closesPoolThenNeedsFreshContext() {
        ((HikariDataSource) dataSource).close(); // corrupts the shared context
        // without @DirtiesContext, the next test class reuses a dead pool
    }
}

// Prefer this for DB tests — rollback instead of rebuilding the context
@SpringBootTest
@Transactional // each test rolls back; context stays cached and fast
class OrderRepositoryTest {
    @Autowired OrderRepository repo;

    @Test
    void savesThenRollsBack() {
        repo.save(new Order("Laptop"));
    }
}

Common Mistakes & Pitfalls

• Using it as a generic reset: It resets a cached ApplicationContext, not every database, broker, file, or remote service.
• Assuming @Transactional covers real-server requests: A request handled on another thread uses a different transaction and may commit.
• Ignoring the mode: A class-level default acts after the class, while a method-level default acts after that method; before modes exist for different isolation needs.