Emil Kantis

@AlexCue987 Should this be refactored to use the similarity package now?

Master is on Gradle 8.6 now, and I'm not sure if we plan to bump Kotlin to 1.9 anymore? Should this be closed @sksamuel ?

Could you verify that viewModelScope is running on the testCoroutineDispatcher every time the Given-code is invoked?

I'm not sure, but re-arranging might cause headaches for others.. Perhaps just removing the possibility to override stuff would make it more consistent?

Shouldn't extension lifecycle hooks always run before their in-spec counterpart, no matter how they were registered? Feels like something we could fix in 6.0 ```kotlin fun extensions(testCase: TestCase): List {...

@sksamuel I think we could consider breaking this with next major? There's been quite a few issues around Iterables

Looks like this is simply not implemented. The JVM executor will define a runner based on the isolation mode, as seen [here](https://github.com/kotest/kotest/blob/master/kotest-framework/kotest-framework-engine/src/jvmMain/kotlin/io/kotest/engine/spec/createSpecExecutorDelegate.kt) The native counterpart resides [here](https://github.com/kotest/kotest/blob/master/kotest-framework/kotest-framework-engine/src/desktopMain/kotlin/io/kotest/engine/spec/createSpecExecutorDelegate.kt). Trying to move...

Sounds like a good idea. :) Close this for the time being?

@polarene It was documented but only in the 5.4 version of the docs. Fixed in https://github.com/kotest/kotest/commit/7b29815cc4b67b14118460b99203b6cbe81e6d9c

@sksamuel please check if my commit makes sense. It fixes the tests and I think the behaviour makes sense