Sam

I'm not sure we can do much about this. If the tests are first, then they are immediately executed. We should clarify the docs though. Or maybe even throw if...

We can't statically enforce this, but I think we can throw runtime errors if afterEach is defined AFTER a test is implemented.

I think we tried release drafter in the past but it doesn't include stuff pushed straight to master (which is another topic I guess :) ). And lots of PRs...

This is what I see:  Are you running from intellij or gradle?

Ok I can duplicate this now.

SpecIrGenerationExtension is a kotest thing, so maybe it's being invoked incorrectly. Are you using the latest gradle plugin for kotest too ? On Wed, 15 Jun 2022 at 06:30, Charles...

I guess this is because JsonNode is iterable, and so it's doing an iterable comparison. @Kantis @ashishkujoy what do you think about dropping "is Iterable" from the checks, and only...

So if you could put beforeContainer inside a container and it only execute for THAT container (and not child containers), that's what you'd expect ? On Fri, 21 Jan 2022...

We could add this and call it beforeScope to make it clear it only runs before that particular scope. On Fri, 21 Jan 2022 at 18:41, Bryan Donovan ***@***.***> wrote:...

We can put this in 5.2, which is due in a month or so.