OliverO2
OliverO2
No, the default is sequential execution: https://kotest.io/docs/framework/project-config.html#parallelism
- Consider making use of kotlin-power-assert which will become part of the standard compiler plugin set ([KT-63607](https://youtrack.jetbrains.com/issue/KT-63607/Migrate-kotlin-power-assert-into-Kotlin-repository)).
Seems like functionality like this is already there: https://github.com/bnorm/kotlin-power-assert > The Gradle plugin allows configuring the functions which should be transformed with a list of fully-qualified function names. ```kotlin //...
I don't currently have an idea of what might work, but things will surely become clearer with some experimentation. It probably makes sense to do this early up and then...
The engine changes in this PR would break #3805.
Not a review at this time, but results from experimenting with the code. Thank you for getting it to this stage! For browser-based JS, results look good already. Also works...
I'm on it as we speak.
Did you consider trying a [snapshot release](https://kotest.io/docs/quickstart#snapshots)?
@vdshb Happy to help. If you try the Wasm target from a snapshot, I'd appreciate it if you'd file an issue in case of problems, or post positive experiences here.
I'm using neither `Dispatchers.setMain` nor the test dispatcher nor anything DI. Some thoughts: * My understanding is that stuff like `advanceUntilIdle` only makes sense if _all_ coroutines are under control...