<@U12AGS8JG> thinking about it, looking at <https:...

# kotest-contributors

[Adam S]

@sam thinking about it, looking at https://github.com/Kotlin/kotlinx-benchmark could help with how Kotest could support KMP targets. It's the exact same situation: discover and launch tests without using JUnit.

For JVM it uses JMH, but the other targets have a custom implementation using a compiler plugin and code generation. However, I know the compiler plugin is overkill and could be replaced with KSP.

[sam]

I think what this is doing is similar to what I had a branch up for. Basically, our compiler plugin would scans for specs, like it does today, and generate a big JS file that does something like:

TestEngine.runWithAllSpecs(a,b,c,d,e,f)

And then from gradle we just launch nodejs with that file.
By doing that we don't need mocha or anything, and we'd get full Kotest support in JS.

Same for Native, except it's just a binary that we launch as a process.

Wasm I know zero about, but I assume we can just run the generated file in the same way, using whatever process is used to execute wasm.

[sam]

At work, we use Kotest exclusively for backend services, and we use it for Android unit tests. Both teams are ready to test M2 + new gradle plugin + updated intellij plugin, so once M2 is out they will be our beta testers, while I move onto either JS or native. Probably JS I guess since that's more common.