Maybe some sort of extension function

# kotest

[LeoColman]

Maybe some sort of extension function

[Adam S]

that would be good - but I can’t see the listener in the context so I don’t think it can be retrieved

[LeoColman]

You could add an extension to Spec

[Adam S]

I’ve tried looking but during debug I couldn’t find the container listener listed anywhere - do you know a method that could retrieve it?

[Adam S]

here’s how it’s registered

class KotestConfig : AbstractProjectConfig() {
  override fun listeners(): List<Listener> =
    listOf(testContainer.perSpec())
}

[Adam S]

I know it works because the tests work

[dave08]

Maybe defaultConfig.listeners in any TestScope?

[dave08]

Maybe search for it there and cast it back to the instance you need.

[Adam S]

I’ve tried looking through loads of methods while debugging and couldn’t see any listener

[Adam S]

[Adam S]

maybe it’s in there somewhere but debugging this many nested lambdas is really difficult

[dave08]

Or just save it as a global lazy val in ProjectConfig and refer to it from there? The listener instance is the same, it just starts and stops the containers every test...

[Adam S]

I’m working on setting something like that up. I just hoped there was an included solution for passing variables into Specs based on config

[sam]

I would do somthing along the lines of what Dave suggests. Make the listener a val in your config. It doesn't even need to be lazy.

object GlobalConfig : AbstractProjectConfig() {
   val testContainer = ...
   override fun listeners(): List<Listener> {
      return listOf(testContainer.perSpec())
   }
}

[sam]

Then you can just do GlobalConfig.testContainer

[sam]

Note that the config is an object here, not a class

[sam]

The container itself still won't be started/stopped until each spec is created