Adding configuration class to SpringBootTest breaks component scan

Question

I am trying to disable real Mongo connection and replace it with Fongo mock in tests.

Here is my test class:

Answer 1

try use

• @SpringBootTest @Import(value = TestConfig.class)

instead of @SpringBootTest(classes = TestConfig.class)

Answer 2

keep @SpringBootTest and then create a class using @TestConfiguration with the beans in as follows:

@TestConfiguration
public class TransactionManagerTestConfiguration {

   @Bean
   public String getDatabaseName() {
       return "FongoDB";
   }

   @Bean
   public Mongo mongo() {
       return new Fongo(getDatabaseName()).getMongo();
   }
}

As per the javadoc: Configuration that can be used to define additional beans or customizations for a test. Unlike regular Configuration classes the use of TestConfiguration does not prevent auto-detection of SpringBootConfiguration.