CODEWITHSUNDEEP
springmockitotestngspring-test
codependent
codependent

Reputation: 24452

Spring Test + Mockito.mock - Spring fails because it tries to load the mocked bean @Autowired dependencies

I can't find out why the following simple scenario is failing: I have a Spring application with a filter that loads a Spring bean from the application context:

public class MyFilter implements Filter{

    private IPermissionService permissionService;

    public void init(FilterConfig filterConfig) throws ServletException {
        WebApplicationContext ac = null;
        try{
            ac = WebApplicationContextUtils.getRequiredWebApplicationContext(filterConfig.getServletContext());
            permissionService = ac.getBean(PermissionServiceImpl.class);

PermissionServiceImpl has an @Autowired attribute dataSource so in my TestNG test, I mock it in the Spring applicationContext:

@Configuration
public class MyFilterSpringTestConfig{

    @Bean
    public IPermissionService permissionService(){
        return Mockito.mock(PermissionServiceImpl.class);
    }

MyTest:

@Test
@WebAppConfiguration
@ContextConfiguration(classes=MyFilterSpringTestConfig.class)
public class MyFilterSpringTest extends BaseSpringFilterTest{

   ...

The problem is that on Spring initialization I get an exception complaining that PermissionServiceImpl's dataSource dependency is not satisfied. Since I wrapped it with a mock, why is it still failing? How could I fix it?

Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [javax.sql.DataSource] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true), @org.springframework.beans.factory.annotation.Qualifier(value=myDataSource)}

Upvotes: 2

Views: 3039

Answers (1)

M. Deinum
M. Deinum

Reputation: 124526

When mocking a class using Mockito (or any other mocking framework) that class is still an instance of the original class. With that comes that it also contains all the annotations and class information with it.

So when you create a mock of the class it still detects all annotations on it and tries to full fill that. I.e. @Autowire other instances.

Either don't use auto wiring or don't mock the class but the interface (which doesn't contain that information).

Upvotes: 5

Related Questions