IllegalStateException: Failed to load ApplicationContext via ContextLoader

Q: Use @SpringBootTest instead

When to use: Use this for standard integration tests.. `@SpringBootTest` automatically finds your `@SpringBootApplication` class and uses it to load the full context. You rarely need `@ContextConfiguration` in Spring Boot.

Q: Specify configuration classes explicitly

When to use: Use this if you must use `@ContextConfiguration` for a custom slice test.. Tell Spring exactly which `@Configuration` classes to load.

Q: Move test to the correct package

When to use: Use this if you are using `@SpringBootTest` but it still fails.. If your test is in a completely different package tree than your main Application class, Spring can't find it. Move the test to a sub-package of the main app.

Q: Add @ConfigurationPropertiesScan

When to use: Use this if your config classes rely on properties scanning.. Ensure your test context knows about your configuration properties classes.

Q: Check for missing @ComponentScan

When to use: Use this if you built a custom config class but it isn't finding your beans.. Your custom `@Configuration` class needs `@ComponentScan` to find `@Service` and `@Controller` beans.

🔴 The Error You're Seeing

Confirm this matches your console output. If it does, you're in the right place.

ERROR LOG

java.lang.IllegalStateException: Failed to load ApplicationContext
	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:132)
	at org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:123)
Caused by: java.lang.IllegalArgumentException: Cannot load an ApplicationContext with a NULL 'contextLoader'. Refer to the API documentation for ContextLoader and SmartContextLoader.

⚡ Quick Fix Works 80% of the time

Use @SpringBootTest instead of @ContextConfiguration to load the default application context.

@SpringBootTest
class MyIntegrationTest { ... }

🧠 Why this Happens

Tap to expand the deep technical explanation

This specific error happens when you use `@ContextConfiguration` without specifying the `classes` attribute, and Spring cannot find a default configuration class (like one annotated with `@SpringBootApplication`). The `ContextLoader` doesn't know what beans to load.

The HITEC City Parking Spot Analogy:

It's like trying to boot a computer from a USB drive, but you forgot to insert the USB drive. The BIOS (ContextLoader) tries to read it, fails, and refuses to start because the boot instructions are missing.

🔁 How to Reproduce Confirm this is your error

Create a test class. Annotate it with `@ContextConfiguration` (with no arguments). Do not put it in the same package as your main `Application` class. Run the test.

🛠️ Solutions (5 Ways to Fix)

Solution 1✓ Most common cause

Use @SpringBootTest instead

👉 Use this for standard integration tests.

`@SpringBootTest` automatically finds your `@SpringBootApplication` class and uses it to load the full context. You rarely need `@ContextConfiguration` in Spring Boot.

@SpringBootTest
class MyIntegrationTest { ... }

Solution 2

Specify configuration classes explicitly

👉 Use this if you must use `@ContextConfiguration` for a custom slice test.

Tell Spring exactly which `@Configuration` classes to load.

@ContextConfiguration(classes = { AppConfig.class, TestConfig.class })
class MyTest { ... }

Solution 3

Move test to the correct package

👉 Use this if you are using `@SpringBootTest` but it still fails.

If your test is in a completely different package tree than your main Application class, Spring can't find it. Move the test to a sub-package of the main app.

// Main app: com.devinhyderabad.Application
// Test should be: com.devinhyderabad.MyIntegrationTest (or com.devinhyderabad.xxx.MyTest)

Solution 4

Add @ConfigurationPropertiesScan

👉 Use this if your config classes rely on properties scanning.

Ensure your test context knows about your configuration properties classes.

@SpringBootTest
@ConfigurationPropertiesScan
class MyTest { ... }

Solution 5

Check for missing @ComponentScan

👉 Use this if you built a custom config class but it isn't finding your beans.

Your custom `@Configuration` class needs `@ComponentScan` to find `@Service` and `@Controller` beans.

@Configuration
@ComponentScan(basePackages = "com.devinhyderabad")
public class TestAppConfig { ... }

📋 Version Notes

Spring Boot 2.x

Standard ContextLoader behavior.

Spring Boot 3.x

Stricter context loading, fails faster on null loaders.

🛡️ How to Prevent This Next Time

Stick to `@SpringBootTest` for integration tests. It handles context loading automatically and is far less error-prone than `@ContextConfiguration`.