Tiberiu Tofan

I think that `beforeRootContainer` would be semantically equivalent to `beforeThisContainerOnly`, but nicer.

I would like to work on this, but I need some guidelines. I don't know if a package level config would be flexible enough. Another use case that I can...

I was thinking that a tag level config might be more flexible and explicit than a package level config.

A typical use case for integration tests is this: start a server on a random available port (using an embedded server or testcontainers) then have multiple tests using the same...

@tonicsoft your solution gave me an idea to combine project lifecycle with spec lifecycle. We need `AfterProjectListener` to be able to register a cleanup stage. The downside is that we...

Small improvement to hide `AfterProjectListener`, that is not needed outside `ProjectConfig`: ```kotlin object EmbeddedContainerExtension : BeforeSpecListener { val embeddedServer: FakeEmbeddedServer by lazy { FakeEmbeddedServer().apply { start() } } override suspend...

And going back to the idea of providing this at tag level, maybe having tag level events could be an option: ```kotlin fun interface BeforeTagListener : Extension { suspend fun...

> Maybe something like: > > ``` > val normalExtension = install(MyExtension(), shared = true) > ``` > > In which case it shares with another spec and the shutdown...

@sksamuel thanks for the suggestion, `SharedTestContainerExtension` was exactly what I needed, but not enough for all cases. I also had some embedded servers that were not test containers. Thus I...

Hi Simon, does this mean replacing kotest altogether or just refactoring the assertions?