Application context is always null

Question

I am using JUnit5, with sureFire version:

<maven.surefire.plugin.version>3.0.0-M5</maven.surefire.plugin.version>

and code

    @ExtendWith(MockitoExtension.class)
    @ContextConfiguration(classes =....ContextConfiguration.class)
    @TestPropertySource({"classpath:application-${env:dev}.properties", "classpath:app-${env:dev}.properties"})
    class TestRunner{
       @Test
       void testService(){
         BeanUtils.getBean(...);
       }
    }


@Service
public class BeanUtil implements ApplicationContextAware {

    private static ApplicationContext context;

    @Override
    public void setApplicationContext(ApplicationContext applicationContext) throws BeansException {
        context = applicationContext; // NOSONAR
    }

    /**
     * Use this method to manually autowire Spring Beans into classes that are not managed by Spring.
     *
     * @param beanClass - Class type of the required bean.
     **/
    public static <T> T getBean(Class<T> beanClass) {
        return context.getBean(beanClass);
    }
}

My ContextConfigurationClass has @ComponentScan directed to BeanUtils class, but the ApplicationContext is always null, not autowired.

I am using @ExtendWith(MockitoExtension.class) cuz i am also mocking in the test.

What JUnit5extension do i need to use in order to init it?

score 2 · Answer 1 · answered Mar 18 '22 at 10:21

2

You should use SpringExtension.

You could also check this post to understand the differences between MockitoExtension and SpringExtension

answered Mar 18 '22 at 10:21

Vladimir Stanciu

1,468
1
7
24

i am using mockito in this classes tho – Johnyb Mar 18 '22 at 10:46
That's fine. You will still be able to mock your beans – Vladimir Stanciu Mar 18 '22 at 10:48
hm, using SpringExtension will break most of the Beans that requires some data from property sources, they just wont get loaded thus bean creation fails – Johnyb Mar 18 '22 at 11:01

Application context is always null

1 Answers1