Consider editing your IntelliJ Kotest configuration template to add these VM options: `-Dkotest.fram...

# kotest

[Rob Elliot]

Consider editing your IntelliJ Kotest configuration template to add these VM options:
-Dkotest.framework.classpath.scanning.config.disable=true -Dkotest.framework.classpath.scanning.autoscan.disable=true

Knocks 5 seconds off running a simple test for me.

(obviously if you’re actually relying on automatically discovered kotest config this is not such a great tip…)

[LeoColman]

I think it could work if it's commented by default. Having autoscan disabled by default is not very intuitive

[Rob Elliot]

It was a suggestion for the end user, not a suggestion for changing the plugin

[LeoColman]

Ah, absolutely 😄

[thanksforallthefish]

and actually if you use extension like spring classpath seems to be needed. I did not investigate much, but disabling scanning prevents autowiring and constructor injection from working properly.

that is a good fix for unit tests still