Is there a way to only enable a project extension ...

# kotest

[dave08]

Is there a way to only enable a project extension if actually needed in one of the test classes being run? I need some testcontainers to come up but only for certain tests, and stay alive for other classes that might need them.

[dave08]

I guess one option could be to use an object as a listener and plug it into the test classes using it.

[sam]

Yeah just add the listener to some specs. Where are you adding it atm

[dave08]

On the project, since I don't want those containers to get destroyed and created for every test class

[dave08]

But I don't want to run all the containers when some test classes don't really need them

[sam]

Do you need them on every test run

[dave08]

Not all of them

[sam]

I don't understand the requirement. If you start the test container at the project level it'll only be started once ?

[dave08]

Like I have some tests that only need postgres, others that only need mysql, etc...

[sam]

And you run them in separate jobs

[dave08]

jobs?

[sam]

Test runs

[sam]

Do you do gradle test postegres and gradle test mysql

[sam]

Do just one gradle test that does them all

[dave08]

No, I usually run single classes in the IDE before/after making changes to code. Before a release, I then run them all.

[sam]

And it's in ide that you don't wanna start them all but just the ones applicable to that test

[dave08]

Yup

[dave08]

Saves development time

[sam]

My phone is about to die but you could add tags to the spec classes and have an if statement in the listeners and only start them if the spec has the appropriate tag