I have a Spring Boot application with a service that caches data, but Kotest isn’t wiping the cache ...

# kotest

[Adam S]

I have a Spring Boot application with a service that caches data, but Kotest isn’t wiping the cache between data-driven tests in an afterEach{} hook - should it?

I thought that withData() would register a test case for each data element, and so afterEach{} would be triggered by the end of each withData(...) {} block

ExampleTest.kt.cpp

[Adam S]

here’s the full test & application

• Kotest 5.5.4
• Kotlin 1.7.21
• Spring Boot 2.7.5

ExampleTestFull.kt.cpp

[Emil Kantis]

what version of kotest-extensions-spring?

[Adam S]

the latest, but I’ll check

[Adam S]

1.1.2

[Emil Kantis]

Change lifecycle mode to Test (default one), root one only resets between root tests 🙂

[Adam S]

same problem :/

[Emil Kantis]

Oh.. hmm.. I wonder if this is because Spring re-uses the context as long as it's not dirtied.

[Adam S]

I’ve added some println statements in here. When I search the logs, I don’t see any AFTER EACH matches. So I don’t think the afterEach {} is triggered, which is strange

e3.kt.cpp

[Emil Kantis]

try adding @DirtiesContext(ClassMode.AFTER_EACH_TEST_METHOD)

[Emil Kantis]

It should work. I made a PR to address this a while back. https://github.com/kotest/kotest-extensions-spring/pull/23

[Adam S]

adding @DirtiesContext(classMode = DirtiesContext.ClassMode.AFTER_EACH_TEST_METHOD) works, but it makes the tests too slow

[Adam S]

and I still don’t see AFTER EACH in the logs

[Emil Kantis]

hehe, of course.. hmm.. wonder if your CustomRootSpec is interfering

[Emil Kantis]

trying to replicate the issue in the kotest-examples-spring-webflux repo

[Adam S]

cool, thanks

[sam]

I don't think after each fires for dynamic tests

[Davio]

Your commit is only for afterTest and beforeTest, afterEach and beforeEach still only work for tests of type TEST (not Dynamic), that still needs a PR I think

[Davio]

This was discussed in this channel recently, you might have to browse back a bit

[Emil Kantis]

Ah, shit. 🙂 Thanks..

[Davio]

Don't know if there has been an actual PR for it but the problem was identified

[Adam S]

https://kotlinlang.slack.com/archives/CT0G9SD7Z/p1666788639534289

[Emil Kantis]

So easy workaround for now would be to use afterTest, if that works for you.

[Emil Kantis]

Looks like someone else also got bit by this: https://github.com/kotest/kotest/issues/3290

[Adam S]

using afterAny {} seems to work

[Adam S]

thanks for your help all

[Emil Kantis]

Should be fixed with https://github.com/kotest/kotest/pull/3300