Sam

I wouldn't want to split the tests because person A might want unit/int tests, and person B might want unit/int/smoke tests and so on. It wouldn't be feasible to cover...

That is a good idea. If we can think of appropriate syntax. Either a map of configs inside project config, Or an AbstractTagConfig that requires you to define the tags...

Maybe something like: ``` val normalExtension = install(MyExtension(), shared = true) ``` In which case it shares with another spec and the shutdown logic is deferred to the end of...

If you restrict to the same instance, then you have to share that instance, unless you mean same input parameters, but then what is "equal'. I need a use case...

There's SharedTestContainerExtension in the latest kotest test containers which will probably do what you want @tibtof

Good idea, we can add an adapter to allow this to reset in property tests too.

We could add one. Any chance you could guide this ? On Thu, 23 Apr 2020 at 04:53, Ben Jones wrote: > We've been using kotest for a while now...

It's the quarkus bit that would new to us. Do you basically instantiate the class via a special way On Thu, 23 Apr 2020, 12:53 Ben Jones, wrote: > I'm...

So @QuarkusTest populates fields or parameters using @Inject. Is it doing anything else beside that? Like are the dependencies it injects just regular deps like outside of a test? Would...

Can you create a PR and tick the box that allows other people to edit it ? We can work on that PR. On Wed, 29 Apr 2020 at 17:29,...