Issue with Mockito and JpaRepository

[YLombardi]

Hello,

I don't know if this an issue with Spring boot data JPA or with Mockito but I encountered a strange behaviour.
I create 2 Controller. In the first, I inject a Service. In the second, I inject a JpaRepository.

Now I create UnitTests for both this Controller.
For the second Controller, I mock the Repository. Everything works fine.
For the first Controller, I mock the Service. The test fail.
It seems to search to inject the Repository whereas it is not used in this Controller.

I create a very simple project to reproduce this behavior :
https://github.com/YLombardi/mockito-spring-jpa-issue

Is it my test that is wrong or a bug ?

[wilkinsona]

Thanks for the sample, @YLombardi. This looks like a bug to me. I'd expect your ControllerAUnitTests to have filtered out ControllerB due to your configuration of @WebMvcTest specifying a single controller:

@WebMvcTest(ControllerA.class)

[bclozel]

The main application class has a @ComponentScan(basePackages = "com.geodis.rt"); removing it solves the issue. Also, the test has a typo where it's checking for a view .andExpect(view().name("aview")); this line should be removed.

[wilkinsona]

Thanks, @bclozel. I was wondering why our tests for this were passing and hadn't spotted that difference . I wonder if there's something we can do to at least make it obvious that the use of @ComponentScan, rather than the aliased attributes on @SpringBootApplication, is going to cause a problem.

Either way, I think we should update the javadoc as it currently says that @SpringBootApplication is "a convenience annotation that is equivalent to declaring @Configuration, @EnableAutoConfiguration, and @ComponentScan".

[wilkinsona]

Now that I know what's going on, this is a duplicate of #10933.

[YLombardi]

Thanks for your answers.
I will see if I can remove the @ComponentScan in my main application.