David Sowerby

@raniejade thanks - I'm not too worried about the number of tests - it is a bit mis-leading but otherwise not too much of a problem. > Yep, I'm going...

Thinking about it further, without guaranteed execution order this structure is invalid isn't it? At any time the test could suddenly go from `Given`, `When`, `Then` to `Then`,`Given`, `When` (or...

@punkisdead thanks for that confirmation. I think this highlights the core of this issue. The current Gherkin DSL in Spek is treating each test step as a test. That leads...

My understanding of the original use case would be something like ... "Because `ExpensivePublisher` is an expensive operation, we only want it to publish when we know it has subscribers"...

> I agree, I think what @GUIpsp and @3xp0n3nt proposed: bus.isDeliverable(Class ) is a good solution. I imagine it will use the same logic as publish -- minus publishing, and...

Thanks for the very quick response. I would say that it is more than a bit extreme ! Your explanation here makes good sense, and I can see that it...

I'll put up a sample project - give me a day or so ...

I've put up a [sample project](https://github.com/davidsowerby/kobalt-kotlintest) which seems to confirm my suspicion that it is a runner change that is needed. I also noticed that when the test run fails...

That was quick. I can see the warnings and the compile error in Build.kt. I've put up a [Gradle equivalent](https://github.com/davidsowerby/kobalt-gradle-kotlintest), but limited both the Gradle and Kobalt builds to KotlinTest3...

Forgot to put a [reference to the utility](https://gitlab.com/dsowerby/serialization-tracer)