Just added `kotest extensions spring 1 0 1` to my maven proj

Question

Just added `kotest extensions spring 1 0 1` to my maven project using surefire to run `kotest framework api jvm 4 6 3` and with no code changes it stopped finding any of my existing specs No errors logged it just silently stops working

Rob Elliot · Answer

Using `KOTEST DEBUG=true` as an env var the end of the maven run looks like this ```Discovery Loading specified classes Discovery Loading of selected classes completed in 0ms After filters there are 3 spec classes JUnit ExecutionRequest org junit platform engine ExecutionRequest configurationParameters=LauncherConfigurationParameters lookups = systemProperties propertiesFile rootTestDescriptor=KotestEngineDescriptor engine kotest INFO INFO Results INFO INFO Tests run 0 Failures 0 Errors 0 Skipped 0 INFO INFO INFO BUILD SUCCESS INFO INFO Total time 23 442 s INFO Finished at 2021 11 24T16 32 34Z INFO ```

sam · Answer

you literally just changed the pom

Rob Elliot · Answer

Yes

Rob Elliot · Answer

Running in IntelliJ via the plugin IntelliJ reports `Test framework quit unexpectedly` but again no further information

sam · Answer

It adds a ConstructorExtension which is automatically used to construct classes

sam · Answer

I guess if that had some kind of error

sam · Answer

I can see why this is failing on 4 6 3 and fix that as 4 6 4 but it will come after thanks giving

Rob Elliot · Answer

OK thanks is there an earlier version of kotest and or the extension you d expect to work

sam · Answer

that extension is used quite heavily most of any extensions

sam · Answer

so you probably have some class lurking about that it can t handle and kotest isn t catching the exception properly is my guess

sam · Answer

are you upgrading to kotlin 1 6 at all

Rob Elliot · Answer

No on 1 5 31 at the moment

sam · Answer

ok so you can t use kotest 5

Rob Elliot · Answer

I ll try debugging in `SpringAutowireConstructorExtension` and see if I can work out where the issue us

sam · Answer

ok in the meantime I ll add a test that deliberately fails a constructor extension to make sure the error is correctly reported

sam · Answer

I need to go offline in an hour to drive to IA for thanksgiving but I can investigate until then

Rob Elliot · Answer

I m not paying you don t stress it If I can work it out I ll raise a PR

sam · Answer

what can I say I take my work and non work seriously haha

sam · Answer

Ok 5 0 does the right thing and reports exceptions

Rob Elliot · Answer

I understand why the error isn t being reported `KoTestEngine execute` does `Try submitAll plan ` but `fun submitAll plan TestPlan = Try ` so you get a nested `Try lt Try lt gt gt ` where the top one is a `Success` but the nested one is a `Failure` so the error reporting `fold` doesn t get triggered

sam · Answer

Ah

sam · Answer

That s 4 6 specific

sam · Answer

If you wanna raise a pr we can deploy

Rob Elliot · Answer

I ll have a go

Rob Elliot · Answer

The problem it s failing to report though is really bizarre `java lang NoSuchMethodError void io kotest mpp LoggerKt log java lang String ` But I can see that method It s on the classpath And anyway why would `kotest extensions spring` being on the classpath make it happen

sam · Answer

Hmm that s a multiplatform thing

sam · Answer

Maybe spring uses it

sam · Answer

And maven gets confused

Rob Elliot · Answer

Yup `kotest extensions spring` depends on `io kotest kotest framework engine jvm 4 4 3`

Rob Elliot · Answer

That ll be it

sam · Answer

Ahh

sam · Answer

We can bump that and deploy 1 0 2

sam · Answer

I ll do that in a minute

Rob Elliot · Answer

Is there a kotest bom I can use to try and prevent accidental dependency reversion

sam · Answer

Yep

Rob Elliot · Answer

Awesome that ll fix it Thanks for your help

sam · Answer

No thank you I didn t do anything lol

sam · Answer

Ok just checked the spring extension and it doesn t use log at all so yeah it s just the version getting changed by bringing it in Nice find

Rob Elliot · Answer

Unfortunately the bom doesn t declare the `kotest jvm` artifacts joys of being on Maven not Gradle

sam · Answer

You could just add that to your build explicitly

sam · Answer

<https search maven org search q=kotest common> ^^ that s where log lives

Rob Elliot · Answer

Yup that s what I m doing