sure

we might have to bump to 3.4.0 then

which I'm happy to do

I cannot do it this weekend, @raulraja? @simon.vergauwen?

Whenever you want, if it's going in 3.4.0 then I want to wait a week at least since we just released 3.3.0 last week 🙂

@pakoito what thing?

Oh yeah, I'll do it

no worries

We release shapshots automatically every build, so once it's merged, you'll have a maven version you can rely on.

If there's anything else you need, you can add it at the same time.

Also check out the KotlinTest intellij plugin if you've not already tried it. Might make your lives easier.

😄

congrats on that btw

how was it writing it?

hard

because of the lack of documentation or documented source

plus it's a slow cycle as you write something and to test it you need to launch another intellij instance with the built plugin.

So a one line change can take 3 minutes to test.

I was just discussing with @LeoColman about writing our own gradle plugin like https://github.com/maiflai/gradle-scalatest for scalatest

then we can offer a complete junit-free experience, and it will be much better

Gradle's implementation of JUnit platform still relies completely on class/method layouts, which make no sense in scalatest/kotlintest/whatever

agreed

There's been open tickets for 18 months. They just don't seem interested in fixing it all

So it means when you have a build in gradle the output is horrible. Whereas scalatest can format it all nicely with a full tree of test names.

Also I think it might mean we can offer a JS runner

Imagine kotlintest for jvm and js

that’d be ideal tbh

kotlintest for property-based test and jest for snapshot tests

and I’d be happy