Hello ppl. Is there anyway to get transactions to rollback for tests in kotest + spring without usin...

# kotest

[Ido Flax]

Hello ppl. Is there anyway to get transactions to rollback for tests in kotest + spring without using annotationSpec?

[LeoColman]

How do you normally rollback spring transactions?

[thanksforallthefish]

so you have an example? we simply use a Spring project extension (https://kotest.io/docs/extensions/spring.html) and annotate the test class, eg:

class ProjectConfig : AbstractProjectConfig() {
  override fun extensions() = listOf(
    SpringExtension,
    SpringAutowireConstructorExtension,
    ... more extensions
  )

  ...
}

@AutoConfigureMockMvc
@SpringBootTest
@Transactional
class MyIntegrationTest(
    private val mockMvc: MockMvc,
    private val testMother: TestMother,
    private val messageOutboxRepository: MessageOutboxRepository,
) : StringSpec()

each test is then rollbacked (because @Transactional annotation)

[Ido Flax]

@DataJpaTest
@ImportAutoConfiguration(RefreshAutoConfiguration::class)
@ContextConfiguration(
    classes = [HiveConfig::class, TableIsDBConfig::class],
    initializers = [DataAccessTestInitializer::class]
)
@ActiveProfiles("integration-test, qa")
@ComponentScan(basePackages = ["com.bla"])
abstract class DataAccessTest : FeatureSpec() {
//spring extension here (i already removed kotest from my pom)
}

[thanksforallthefish]

looks to me you are just missing the @Transactional annotation in there, then it should work.

I don’t use test slices, but I think @DataJpaTest configures everything related to persistence, so transaction should definitely work

(I don’t use test slices because coincidentally I think they make your test suite slower, since the application context is memoized if all tests share the same context it is initializated only once, if you start using test slices you get multiple contexts, data, web, jackson, etc etc)

[Ido Flax]

@thanksforallthefish I thought i had @Transactional on it. weird. I’ll try again with kotest and feature spec. Re slices, yeah i get you, but in this case i’m writing tests for a data access module so it only does DA

[Ido Flax]

Seems i had the transactional annotation on the tests themselves instead of the class. i think that was the issue

[Ido Flax]

Scratch that, still no transaction rollback

[thanksforallthefish]

try to import TransactionAutoConfiguration as well, but if you say that with annotationspec transactions work it is probably not that

[thanksforallthefish]

at this point though, I am honestly out of ideas, I would need to see your project (and have the time, which is also a luxury in this period)

[Ido Flax]

@DataJpaTest(
    properties = [
        "spring.application.name=datamatic-tableis-IT",
        "spring.cloud.bootstrap.enabled=false",
        "atlas.rest.address=<http://localhost:10200>"
    ]
)
@ImportAutoConfiguration(RefreshAutoConfiguration::class)
@ContextConfiguration(
    classes = [HiveConfig::class, TableIsDBConfig::class],
    initializers = [DataAccessTestInitializer::class]
)
@ActiveProfiles("integration-test, qa")
@ComponentScan(basePackages = ["com.bla"])
@Transactional
abstract class DataAccessTest : AnnotationSpec(){
    override fun extensions() = listOf(SpringExtension)
}

[Ido Flax]

Here’s my current setup, which doesn’t seem to work

[Ido Flax]

it seems to be rolling back for test failures though:

[org.springframework.test.context.transaction.TransactionContext()] - Rolled back transaction for test:

[Ido Flax]

I might be wrong. looking into it

[Ido Flax]

Ok i think the issue is that i was expecting it to rollback DDL statements, which in mysql are not transactional. mwep 😕

[thanksforallthefish]

curiosity, why would you want DDL rollbacked? that would make your tests super slow, since all tables would need to be recreated on each test?

anyway, good you found out 👍