Spring Boot切面类@Autowired字段测试时为null问题求助

Hey there, let's work through this frustrating issue where your aspect's autowired fields work fine in production but turn up null during unit tests. I've seen this pop up a lot, so here are the most common fixes to try:

• Make sure your test loads the Spring context
  Plain @Test annotations won't fire up the Spring container—so none of your beans (including the aspect and its dependencies) get initialized. Swap it out for @SpringBootTest at the top of your test class. This tells Spring to boot up the full application context, just like when you run the app normally, which lets autowiring do its job. If you don't need the full context, you can use @ContextConfiguration to specify exactly the configuration classes or components (like your aspect) that need to be loaded.

• Verify your aspect is a Spring-managed bean
  Your aspect class needs to be detected by Spring's component scanner. Double-check that it has the @Component annotation (pair it with @Aspect—since @Aspect alone doesn't register it as a bean). Alternatively, if you're defining it via a configuration class, make sure you're using @Bean to create the aspect instance there. If Spring doesn't manage the aspect, it won't process the @Autowired annotations inside it.

• Don't manually instantiate the aspect in tests
  If you're doing something like MyAspect aspect = new MyAspect() in your test, that's a problem. Spring only injects dependencies into beans it creates and manages. Instead, use @Autowired to inject the aspect into your test class, just like you would any other bean. That way, you're working with the Spring-managed instance that has all its dependencies wired up.

• Check test profile configurations
  If you're using different profiles for testing, make sure the dependencies your aspect relies on are properly defined in the test profile. For example, if your autowired field is a service that's mocked or configured differently in tests, ensure that bean is present in the test context. You can use @ActiveProfiles("test") to explicitly activate the test profile in your test class.

• Use Spring-aware testing utilities if using Mockito
  If you're mixing Mockito with Spring tests (like using @MockBean to replace a dependency), make sure you're still using @SpringBootTest instead of just @ExtendWith(MockitoExtension.class). The Mockito extension alone doesn't load the Spring context, so autowiring won't work. Combining @SpringBootTest with @MockBean lets you mock specific beans while keeping the rest of the context intact.

Give these steps a try—nine times out of ten, one of these will fix the null pointer issue with your aspect's autowired fields in tests!

内容的提问来源于stack exchange，提问作者193michalll