SpringBoot 2.x, JUnit5 and DatabaseRider configuration woes

It seems that getting this combination of tools to work together isn’t sufficiently documented, I found the examples to be lacking. However, after a couple of hours of experimentation I was able to assemble a meta-annotation for myself that works as expected:

@SpringJUnitConfig
@DBUnit(
    caseInsensitiveStrategy = Orthography.LOWERCASE,
    cacheConnection = false,
    dataTypeFactoryClass = PostgresqlDataTypeFactory.class
)
@TestExecutionListeners(
    value = {
        DBRiderTestExecutionListener.class,
        TransactionalTestExecutionListener.class,
        DependencyInjectionTestExecutionListener.class,
        DirtiesContextTestExecutionListener.class
    },
    mergeMode = TestExecutionListeners.MergeMode.MERGE_WITH_DEFAULTS
)
@DirtiesContext
@SpringBootTest(
    webEnvironment= SpringBootTest.WebEnvironment.NONE
)
@Transactional
@Target({ElementType.TYPE})
@Retention(RetentionPolicy.RUNTIME)
@Inherited
public @interface DBIntegrationTest {
}

Am I doing too much configuration here? Is there something I missed? I’m glad that I was able to find a working configuration, but the samples/examples that I have seen published lead me to believe that a simpler configuration should have been possible…

[arhohuttunen]

I agree, this is something only Spring specific.

A lot of this was hidden because I didn’t know that @DataJpaTest adds a @Transactional annotation, and now I’m considering changing the default and cleaning up some tests the dbunit way. They mostly already work because of the default seeding strategy anyway.

[mutsys]

no problem. i will put together an example repo for you that reproduces the issue.