@Oliver.O and I have been investigating improving Kotest support for JS and Wasm tests (mostly focused on supporting nested testing). (
mostly in this thread)
TL;DR:
• integrating with existing JS frameworks is hard (they just don't support fully async dynamic nested tests)
• integrating with Kotlin Gradle Plugin JS tests is hard (KGP parses log messages, but the parser is overly opinionated and tightly coupled, and is internal - so depending on this would be difficult)
• Good news: creating a custom JS launcher should be possible,
but it requires lots of work (need a local dev server (Ktor) to host the compiled Kotlin/JS .js files, and
Playwright to run browser tests).
• One significant part is reporting the test results to Gradle, which requires creating a custom JUnit TestEngine, because
Gradle doesn't support any other way of reporting tests. (although we could decide this isn't necessary?)
@sam (or other contributors), can you help with something? I came across your message from a while ago regarding future JUnit platform integration. Is it still the idea that Kotest will stop using JUnit platform? Might that affect our plans?
https://kotlinlang.slack.com/archives/CT0G9SD7Z/p1666957973023689?thread_ts=1666788639.534289&cid=CT0G9SD7Z