OliverO2

Seems like `wasmJsBrowserTest` fails with a single test exceeding the (presumably karma) timeout of 30 seconds. I could take a look cannot promise results today.

Why does this lead to the timeout? I'd expect it the test run to finish on `wasmJsBrowserTest` without reporting any test. I'll try to investigate,

The test times out because the dependency `implementation(projects.kotestFramework.kotestFrameworkEngine)` is missing in `commonTest`. For Wasm, the function `startUnitTests` is missing in that case: https://github.com/kotest/kotest/blob/2f9215c2f0519e08fe94ee6b37431fde736c1424/kotest-framework/kotest-framework-engine/src/wasmJsMain/kotlin/io/kotest/engine/KotlinJsTestFramework.wasmJs.kt#L73-L79 The Kotlin test framework crashes as it...

That's correct, any JS platform test (including `wasmJs`) would fail if it requires a `runTest` invocation. Kotest effectively does not fully self-test on non-JVM targets anyway due to the missing...

Apparently, the above commit does not fix this issue: https://github.com/kotest/kotest/actions/runs/9616156154/job/26525088171?pr=4114

Could you check whether the system property `kotest.tags="CustomTest"` is actually passed from the command line to the forked surefire JVM? You can try changing the `argline` setting in your POM...

Initially, you wrote `kotest.tags=CustomTest`, the latest post says `kotest.tags=Custom`. Can you provide a minimal reproducer?

You could also run the test with debug logging enabled like this: ``` env KOTEST_DEBUG=true ./mvnw test -Dkotest.tags="CustomTest" ``` Then you should find a file `kotest.log`. Look inside for a...

That's unfortunately hardcoded in your Kotest version (this has been corrected since). Could you temporarily create the directory and look at the log file there?

The "Active tags" log entry has been in Kotest since 2021. Kotest 5.6.0 is of April 2023. Please post the contents of the log file from the first line up...