OliverO2

> Does this mean the extension runs in a coroutine that is attached to the spec level coroutine? Yes, its coroutine becomes a direct child of the spec-level coroutine. You...

The tests fail on JS platforms because of `IllegalStateException: No SpecContextElement`. For whatever reason, the relevant coroutine context when invoking the function returned by `BeforeSpecListenerInterceptor.intercept` on these platforms looks like...

The `SpecContextElement` is missing on non-JVM platforms because the `SpecInterceptorPipeline` is only created by `SpecRunner` derivatives. These in turn are only created by `JvmSpecExecutorDelegate`. So the `SpecInterceptorPipeline` is not present...

> Do you have some concrete examples of what we could do to improve things? I have a broad idea, like making everything a Spec can do local to a...

I've created a minimal example of what I'm imagining: https://github.com/OliverO2/kotlin-test-framework-prototype

Thanks for looking into it! I might not have presented my pain points in the best possible way so far, and I think the best way forward is to produce...

> That might be just because you're not working in this codebase every day. Exactly. The same thing can also happen to my future self with code I wrote. >...

That's fine! Turned out that to prove my point I actually had to draw [the rest of the owl](https://casnocha.com/2010/11/how-to-draw-an-owl.html). Hope there's some value in having done so.

From the perspective of new test frameworks coming to the JVM, like [TestBalloon](https://github.com/infix-de/testBalloon) for Kotlin, this is paramount: > The idea is not for Gradle to implement its own discovery...

I suggest to replace * `Uuid.parse` with `Uuid.fromHexDashString`, * `Uuid.parseHex` with `Uuid.fromHexString`. This would result in * better discoverability in the IDE via `UUID.from` + completion, * consistency with other...