OliverO2

I haven't looked at the details, but isn't `coroutineTestScope` (which introduces its own notion of time) inherently incompatible with - using Kotest's `timeout` configuration, and - using another dispatcher like...

Understood. To avoid misinterpretations, `Thread::sleep` could be used in such cases. If I understand things correctly, the `TestDispatcher` from `kotlinx-coroutines-test` has i[ts own timeout setting, defaulting to 10 seconds](https://github.com/Kotlin/kotlinx.coroutines/tree/master/kotlinx-coroutines-test#timeout). The...

If your use case is actually blocking code (test taking multiple minutes without cooperative cancellation in between), you should really use Kotest's `timeout` parameter in conjunction with `blockingTest = true`,...

Actually, Kotest is not involved here. If `coroutineTestScope` is true, it wraps the test in a `TestCoroutineInterceptor`, which uses `runTest` from `kotlinx-coroutines-test` to run it. Kotest does not provide additional...

Created https://github.com/Kotlin/kotlinx.coroutines/pull/4099.

Currently, you cannot. For an immediate solution, I'd consider invoking `runTest` directly. For an integrated fix, a PR would be the way to go.

Maybe adding the last line of this to `.github/workflows/master.yml` would suffice? ``` jobs: linux: strategy: matrix: target: - :kotest-framework:kotest-framework-multiplatform-plugin-gradle:publish ```

> 6.0 should be the next release once kotlin 2.0 is stable. My testing with Kotlin 2.0 release candidates suggests that Kotest 5.9.0 will most probably work just nicely with...

This will have to wait until support for the `wasmWasi` target lands in **kotlinx.coroutines**: https://github.com/kotest/kotest/blob/13b7fbcebc1ff34c4d24b009972652799f9d38da/buildSrc/src/main/kotlin/kotest-js-conventions.gradle.kts#L19

> 1. Error output is not printed. I just see This is about a Node.js test, right? If so, the issue is #3329, which has been around for a while...