Sam

> I have extended your test so that it will additionally cover an extension configured project-wide and case-specific (the latter configured differently, intended to override the project-wide setting) . This...

Ok great so my changes to the test executor ended up fixing his too (on JVM).

I don't think this would ever happen. It's hard enough trying to get kotest to run on JUnit successfully given how much more flexible Kotest is, and we've put a...

Broken on the following issue in kotlin: https://youtrack.jetbrains.com/issue/KT-66470/False-overload-resolution-ambiguity-when-both-vararg-and-collection-match-with-a-trailing-function-with-a-parameter

> My recommendation is that as an essential fix, Kotest should find a way to catch this exception and report a more informative error message to the user. Otherwise, the...

Coming late to this discussion. To be honest I'm not sure Kotest even needs its own scanning. I added it originally because I didn't realize at the time that Gradle...

Yeah please raise a PR. Good idea!

Yeah I think so. We can't have the poor performance. 6.0 should be the next release once kotlin 2.0 is stable.

The idea to derive kotest assertion is great, but not the mocking bit. As @LeoColman says we want to keep mocking out. Can you describe a bit more about how...

Looks good to me. Happy to merge if @Kantis is happy.