"Wrong usage of mappers factory" should not be warning in Tests scope

[GTOL]

I think it should not show warning in unit test code with no component scan.

@InjectMocks
private JobService jobService;
@Spy
JobEntityMapper jobEntityMapper = Mappers.getMapper(JobEntityMapper.class);

[thunderhook]

Hi @GTOL!

Thanks for reaching out. Haven't seen a construct like this. Can you give a litte more insight how your test setup looks like?

It seems that your mapper uses a component model like Spring in production. And in the test it should be initialized via Mappers.getMapper(JobEntityMapper.class). How does this work in your case? What about its dependencies?

We're using constructor injection and test our spring mappers by initializing them by hand (or providing mocks via the constructor)

Thanks in advance.

[GTOL]

Hi @thunderhook, thanks for your reply!

Yes, we use Spring in production.

The code snippet I shared is for testing the JobService class, which relies on JobEntityMapper to convert entities into DTOs. The test class is only annotated with @ExtendWith(MockitoExtension.class), so Spring’s dependency injection isn’t available in this context.

In principle, we should mock all of JobService’s dependencies. However, to reduce effort, we decided to use the real JobEntityMapper with the @Spy annotation, since the mapper itself will be covered by its own dedicated unit tests. That’s why we initialize it with Mappers.getMapper(JobEntityMapper.class). And that is where we saw the warning: "Wrong usage of mappers factory".