Is it expected for `AbstractProjectConfig` to be p...

# kotest

[Kirill Zhukov]

Is it expected for AbstractProjectConfig to be picked up by Kotest in a KMP project? It doesn’t seem to be working for me 🤔
https://github.com/kotest/kotest/issues/3462

[Emil Kantis]

the auto-detection depends on classpath scanning, so yes - it doesn't work on other targets

[Kirill Zhukov]

@Emil Kantis, do you mean it doesn’t work with non-jvm targets?

[Kirill Zhukov]

That would make sense

[Kirill Zhukov]

But I’ve seen this problem locally with jvmTest

[Emil Kantis]

Graalvm?

[Kirill Zhukov]

amazon corretto

[Emil Kantis]

Odd.. it should definitely work for jvm targets (as far as I can tell).. if you can produce a MRE I'd be happy to take a look

[Kirill Zhukov]

Super weird, it’s working now 😑

[Kirill Zhukov]

Maybe I was missing gradle sync or something 😕

[Oliver.O]

Actually, auto-detection works just fine on non-JVM targets: For K/Js and K/Native you have to add the Kotest Gradle plugin to the build. This will then activate a compiler plugin, which in turn picks up AbstractProjectConfig.

[Kirill Zhukov]

I’ve had the plugin applied the whole time actually! I think I’m getting tripped up by isolationMode. I had it set InstancePerTest in the global project config and didn’t seem to be picked up on K/N. As it actually turns out, it doesn’t seem to be applied at all when set in the spec itself. So this test passes on JVM but fails on K/N:

class Foo : FunSpec({
  isolationMode = InstancePerTest
  var count = 0

  test("count is 1") {
    count++
    count shouldBe 1
  }

  test("count is still 1") {
    count++
    count shouldBe 1
  }
})

[Kirill Zhukov]

😭
https://github.com/kotest/kotest/issues/3414