6.0.0.M2 is published
# kotest-contributors
s
6.0.0.M2 is published
kotest intensifies 5
👍🏼 1
e
Care to send new IJ plugins? 🙂
s
kotest-intellij-plugin-1.3.0-SNAPSHOT-2024.2.2.zip
kotest-intellij-plugin-1.3.0-SNAPSHOT-2024.3.1.zip
e
2024.3.2 also? 🙏
s
bottom one will work
e
ah ok
Using Kotest 6.0.0.M2
Both when running using the spec arrow and the leaf tests
Same when running from command-line
Copy code
$> ./gradlew kotest           
Calculating task graph as no cached configuration is available for tasks: kotest
Type-safe project accessors is an incubating feature.

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':autoinvoice'.
> Could not create task ':autoinvoice:kotest'.
   > org/jetbrains/kotlin/gradle/tasks/KotlinCompile
I used gradle convention plugins to apply the Kotlin-jvm plugin to my project, and then the Kotest-plugin directly from the projects
build.gradle.kts
. I.e
Copy code
// foo/build.gradle.kts
plugins {
  id("my-kotlin-conventions")
  id("io.kotest")
}
I seem to get further after applying the Kotest plugin in the same convention plugin as the Kotlin JVM plugin.
s
Do you have the multiplatform one too?
e
no
Plugin creates
kotest
tasks for projects which don't depend on Kotest runner.
Copy code
> Task :boneo:vitec:kotest FAILED
Error: Could not find or load main class io.kotest.engine.launcher.MainKt
Caused by: java.lang.ClassNotFoundException: io.kotest.engine.launcher.MainKt
Since I apply it with the convention now, I get kotest in every project, even if I don't have any tests there 🙂 Perhaps it could detect that and skip creating tasks
Aside from the small issues, this is fucking amazing 🤩
s
There's a bug with them clashing as they both call their extension "kotest"
e
Will the kotest gradle multiplatform plugin even be needed after this?
Feels like the new plugin would(could) make the old one obsolete
s
we could merge the two (if that's possible) but one is doing the compiler plugin support and one is running tests via gradle
so they're not doing the same thing, but I suppose in theory why have two
you will ultimately need both anyway for multiplatform I guess