I have been using KoTest quite extensively over th...

# kotest

[dirk.dittert]

I have been using KoTest quite extensively over the last couple of months and do like it as a testing framework. There is one thing that is driving me crazy because it is constantly breaking my development flow. That is, that I can't just keep running Specs. IntelliJ shows "Current File" and Run/Debug gets disables. Sometimes when I delete the run configuration it will work a couple more times but will eventually break again. This is an absolute killer for productivity as I keep running my tests constantly while my code is evolving.

I believe that this is the bug that was already reported by Geoffry:
https://github.com/kotest/kotest/issues/4646

[LeoColman]

We're tweaking the IJ plugin a lot for 6.0, so let's wait a bit for that. We already have some internal beta builds under test.

Meanwhile, I think a quick fix is to run the spec via Gradle. It will place a gradle task as the last executed task and then the shortcut will probably work

[dirk.dittert]

My workaround is to run contexts. That seems to work better. Also, I noticed that I can't double click on failed tests in the tree. You need to navigate through the stack trace to where the error occurs.

[sam]

Can you screenshot that can't double click thing

[dirk.dittert]

You mean like create a Gitub issue for that?

[sam]

Like screen shot the ide as not sure what you mean

[sam]

In the test result window?

[LeoColman]

I think it's on the top

[LeoColman]

It won't go to "Last ran task" and the button will become a dropdown for "Current File"

[LeoColman]

That for the first part

[LeoColman]

For do uble clicking, it should be the same as "Go to source" or pressing f4 with a test selected

[LeoColman]

So yes, it's in the test result window, specifically with failing tests selected

[dirk.dittert]

I am talking about that on here

[LeoColman]

Running through gradle doesn't support going to source, so double clicking won't work

[LeoColman]

It should work for the root to go to file

[dirk.dittert]

It seems to be dependent on what is being run.

[dirk.dittert]

If you run a single test, then it goes to source

[dirk.dittert]

if you run more than one (e.g. a context or a spec), it does not

[LeoColman]

when you run a single test you are using Kotest, as only it is capable of running single tests.
If you run the spec it runs via gradle

At least this is the default behavior on my IDE

[dirk.dittert]

I just tried in my IDE: that behavior differs from what happens with JUnit. There, a double click always navigates to the test. I am running the JUnit tests through Gradle.

[LeoColman]

Yes, the behavior is different from running using Kotest to running with Gradle. Junit is integrated with gradle, that's why Kotest can't do the same thing

[LeoColman]

(and that's why we're developing our own plugin to work with gradle)

[dirk.dittert]

Thanks for clarifying. I don't know about what can be customized by plugins and what can't be customized. I just noticed that my finger memory doesn't work anymore 🙂

[LeoColman]

I understand your pain 😢

[sam]

The new plugin already does this properly.

[sam]

It works with M2 (if you're on a JVM project)