Chris Kocel

I would rather be able to leverage [opentest4j](https://github.com/ota4j-team/opentest4j) support in kotest, the assertion I put in the description is a sample.

@yury-s I can, but it won't be functional since the page I use is internal. If it's not important I can create it anyway

@mxschmitt I will get back to you in a couple of days - I will un-suppress error logging and see if it still occurs

@benhalpern is there any workaround for this?

@benhalpern do you have plans to resolve those caching isues?

@szpak I managed to put some non working example - https://github.com/kkocel/mutation-testing

It's more about implementation concerns - I've seen `bindTo` methods in some libraries that use `synchronized` keywords or `ReentrantLock` and micrometer implementations that do not use such mechanisms.

Yes, I use Gradle plugin. My Junit5 dependencies: ``` | +--- org.junit.jupiter:junit-jupiter:5.11.3 -> 5.8.2 | | +--- org.junit:junit-bom:5.8.2 -> 5.11.3 | | | +--- org.junit.jupiter:junit-jupiter:5.11.3 -> 5.8.2 (c) | |...

@hcoles I updated my config: ``` pitest { pitestVersion = "1.17.2" junit5PluginVersion = "1.1.2" avoidCallsTo = setOf("kotlin.jvm.internal") mutators = setOf("STRONGER") exportLineCoverage = true verbose = true targetClasses = setOf("com.example.*") targetTests...

@hcoles I use "1.15.0" so I guess it's the latest one.