OliverO2

Apparently a regression introduced by #3649, so possibly only affecting `beforeSpec`.

Running each test in its own coroutine makes the most sense to me (even if it is the first/only test in a spec), as any problems with non-terminating coroutines will...

Current status: Waiting for resolution or workaround regarding [KT-64357](https://youtrack.jetbrains.com/issue/KT-64357) K/Wasm: "CompileError: WebAssembly.Module(): Invalid types for ref.test: local.get of type externref has to be in the same reference type hierarchy as...

Status update: There is a problem with `wasmJs` test invocations. While Mocha functions like `describe` and `it` are available with `js` tests, they are not with `wasmJs`. This prevents execution...

@eygraber No, AFAIK there is nothing blocking this technically, it's just a matter of review resources, since this is not exactly a tiny PR. Also, we'd possibly have to unbundle...

@Kantis, @sksamuel Before merging this, can we decide what to do with `kotest-extensions-http`? It builds with `kotest-js-conventions`, which would include Wasm/JS. It also uses Ktor dependencies, which have Wasm support...

Moving `kotest-extensions-http` to a separate repo should happen in a separate PR. For now, I have reverted the changes that would require Ktor 3.0.0-wasm2 and restricted the extension to build...

Yes. This one is complete and ready. How best to merge it given Sam's intention of getting out 5.8.1 this week (see kotlinlang Slack)?

If there are no objections, I'd merge this within 24 hours so that other PRs can align.

~`finalizeSpec` seems to work as documented:~ * ~with `InstancePerLeaf`, you'd get 2 invocations for leaf tests "b", "c".~ * ~with `InstancePerTest`, you'd get 3 invocations, 1 for container "a", 2...