Spring-Boot module based integration testing

前端 未结 2 1500
逝去的感伤
逝去的感伤 2021-01-12 23:17

I have a multi-module Spring-Boot project. I was wondering how I can set up integration testing just to test Spring Data JPA repositories? The following approach fails with

相关标签:
2条回答
  • 2021-01-12 23:40

    I resolved this by having the following test config class.

    @Configuration
    @EnableAutoConfiguration
    @ComponentScan
    @PropertySource("classpath:core.properties")
    class TestConfiguration {
    }
    

    core.properties is also used by the main application and it contains datasource information. @IntegrationTest annotation can be removed on the test class.

    I also added the following to the module as dependencies:

    testRuntime 'javax.el:javax.el-api:2.2.4'
    testRuntime 'org.glassfish.web:javax.el:2.2.4'
    
    0 讨论(0)
  • 2021-01-12 23:54

    As Marten mentioned, @IntegrationTest should only be used when you need to test against the deployed Spring Boot application (e.g., deployed in an embedded Tomcat, Jetty, or Undertow container). So if your goal is to test your repository layer in isolation, you should not use @IntegrationTest.

    On the other hand, if your tests require specific Spring Boot functionality (in contrast to standard Spring Framework functionality, semantics, and defaults), then you will in fact want to annotate your test class with @SpringApplicationConfiguration instead of @ContextConfiguration. The reason is that @SpringApplicationConfiguration preconfigures the SpringApplicationContextLoader which is specific to Spring Boot.

    Furthermore, if you want your repository layer integration tests to run faster (i.e., without the full overhead of Spring Boot), you may choose to exclude configuration classes annotated with @EnableAutoConfiguration since that will auto-configure every candidate for auto-configuration found in the classpath. So, for example, if you just want to have Spring Boot auto-configure an embedded database and Spring Data JPA (with Hibernate as the JPA provider) along with entity scanning, you could compose your test configuration something like this:

    @Configuration
    @EnableJpaRepositories(basePackageClasses = UserRepository.class)
    @EntityScan(basePackageClasses = User.class)
    @Import({ DataSourceAutoConfiguration.class, HibernateJpaAutoConfiguration.class })
    public class TestRepositoryConfig {}
    

    And then use that configuration in your test class like this:

    @RunWith(SpringJUnit4ClassRunner.class)
    @SpringApplicationConfiguration(classes = TestRepositoryConfig.class)
    @Transactional
    public class UserRepositoryTests { /* ... */ }
    

    Regards,

    Sam

    p.s. You might find my answer to the following, related question useful as well: Disable security for unit tests with spring boot

    0 讨论(0)
提交回复
热议问题