What's the easiest way of debugging Kotest interna...

# kotest

[Giorgio Vespucci]

What's the easiest way of debugging Kotest internals?
Are there some switches to enable debug level of logging to see what "it's doing"?
I'm affected in my work project by a behavior that HANGS A LOT before starting to execute the tests.
I cannot upgrade from V5.6.x to v5.9.x due to this.
I only see an infinite series of

Warning: Kotest autoscan is enabled. This means Kotest will scan the classpath for extensions that are annotated with @AutoScan. To avoid this startup cost, disable autoscan by setting the system property 'kotest.framework.classpath.scanning.autoscan.disable=true'. In 6.0 this value will default to true. For further details see <https://kotest.io/docs/next/framework/project-config.html#runtime-detection>

Setting the mentioned property to true doesn't help.
Thank You
CC @Matteo Mirk

[Matteo Mirk]

I've already ran into the autoscan issue, there's also another flag to disable to eliminate this initial delay due to classpath scanning. In a project of mine i have this settings:

kotest.framework.classpath.scanning.config.disable=true
kotest.framework.classpath.scanning.autoscan.disable=true

see if this helps!

[Matteo Mirk]

Moreover, where do you have your config file? Mine is located at src/test/resources/kotest.properties and it works. Other paths and file names may not be read by Kotest

[sam]

You could give 6.0.0 M3 a go too

[sam]

in 6+, that classpath stuff is all removed, so its faster overall

[Matteo Mirk]

Thanks for the info Sam! Will that feature be completely removed or just opt-in?

[sam]

Removed. It's not really needed and just slowed everything down