NoSuchBeanDefinitionException: No qualifying bean of type 'com.devinhyderabad.service.UserService' available

Q: Create the real implementation

When to use: Use this if you wrote the interface but haven't written the implementation yet.. Spring needs the real bean to exist before @MockBean can replace it.

Q: Fix Component Scan paths

When to use: Use this if the implementation exists, but is in a package outside the main app's scan path.. If your test uses `@SpringBootTest`, it scans from the main Application class package. If the service is in a sibling package, it won't be found.

Q: Use @Mock instead of @MockBean

When to use: Use this if you are writing a pure unit test and don't need to start the Spring context.. If you don't need Spring's dependency injection, use Mockito's `@Mock` and `@InjectMocks`. This doesn't require the real bean to exist.

Q: Import specific configurations

When to use: Use this if you are using a sliced test (like @WebMvcTest) and the service isn't picked up.. Sliced tests don't scan the whole context. You must explicitly import the service class.

Q: Provide the bean in a @TestConfiguration

When to use: Use this if you want to provide a stubbed implementation just for testing.. Define a test-specific configuration class that creates the missing bean.

🔴 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
...
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.devinhyderabad.service.UserService' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)}
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveNamedBean(DefaultListableBeanFactory.java:1336)

⚡ Quick Fix Works 80% of the time

Ensure the real implementation class (e.g., UserServiceImpl) is annotated with @Service and is in a scanned package.

@Service
public class UserServiceImpl implements UserService { ... }

🧠 Why this Happens

Tap to expand the deep technical explanation

In Spring Boot 3, `@MockBean` works by finding the *real* bean in the application context and replacing it with a Mockito mock. If the real bean doesn't exist (e.g., you forgot the `@Service` annotation, or it's in a non-scanned package), Spring cannot find anything to replace, and throws `NoSuchBeanDefinitionException`.

The HITEC City Parking Spot Analogy:

It's like ordering a fake cake for a movie set. The prop department (Spring) asks the bakery for the real cake recipe to copy it, but the bakery says, 'We don't make that cake.' The prop department can't make a fake version of something that doesn't exist.

🔁 How to Reproduce Confirm this is your error

Create a `UserService` interface with no implementations. Write a test using `@MockBean private UserService userService;`. Run the test.

🛠️ Solutions (5 Ways to Fix)

Solution 1✓ Most common cause

Create the real implementation

👉 Use this if you wrote the interface but haven't written the implementation yet.

Spring needs the real bean to exist before @MockBean can replace it.

@Service
public class UserServiceImpl implements UserService { ... }

Solution 2

Fix Component Scan paths

👉 Use this if the implementation exists, but is in a package outside the main app's scan path.

If your test uses `@SpringBootTest`, it scans from the main Application class package. If the service is in a sibling package, it won't be found.

@SpringBootTest
@ComponentScan(basePackages = "com.devinhyderabad")
class MyTest { ... }

Solution 3

Use @Mock instead of @MockBean

👉 Use this if you are writing a pure unit test and don't need to start the Spring context.

If you don't need Spring's dependency injection, use Mockito's `@Mock` and `@InjectMocks`. This doesn't require the real bean to exist.

@ExtendWith(MockitoExtension.class)
class MyTest {
    @Mock
    private UserService userService; // Doesn't need Spring context

    @InjectMocks
    private UserController userController;
}

Solution 4

Import specific configurations

👉 Use this if you are using a sliced test (like @WebMvcTest) and the service isn't picked up.

Sliced tests don't scan the whole context. You must explicitly import the service class.

@WebMvcTest(UserController.class)
@Import(UserServiceImpl.class)
class UserControllerTest { ... }

Solution 5

Provide the bean in a @TestConfiguration

👉 Use this if you want to provide a stubbed implementation just for testing.

Define a test-specific configuration class that creates the missing bean.

@TestConfiguration
public class TestConfig {
    @Bean
    public UserService userService() {
        return new UserService() { /* stub methods */ };
    }
}

📋 Version Notes

Spring Boot 2.x

@MockBean sometimes silently registered a new bean if one didn't exist.

Spring Boot 3.x

Stricter context validation. Fails fast if @MockBean cannot find a real bean to replace.

🛡️ How to Prevent This Next Time

Use `@MockBean` only to replace existing beans in integration tests. For pure unit tests, prefer Mockito's `@Mock` and `@ExtendWith(MockitoExtension.class)`.