Is there a simple way to run an individual Spec fr...

# kotest

[xenomachina]

Is there a simple way to run an individual Spec from IntelliJ? This works on a previous version of our code base that used kotlintest 3.4.2, but with kotest 4.1.0 the finest-grained thing I can run from IntelliJ seems to be the entire package which contains many specs.

I tried installing the kotest plugin (1.0.2, which says it's for 4.1.0) and restarting IntelliJ, but I still get no "Run" options on individual specs.

[sam]

Sounds odd. With 1.0.2 and 4.1.0 you should see the play icons on every test.

[sam]

are you sure the project doesn't have 3.4.2 deps lurking about

[xenomachina]

$ ./gradlew dependencies | egrep 'ko(tlin)?test' | sed -e 's:^.*- io\.:io.:' -e 's: .*::' | sort -u
io.kotest:kotest-assertions-core-jvm:4.1.0
io.kotest:kotest-assertions-shared-jvm:4.1.0
io.kotest:kotest-common-jvm:4.1.0
io.kotest:kotest-core-jvm:4.1.0
io.kotest:kotest-extensions-jvm:4.1.0
io.kotest:kotest-property-jvm:4.1.0
io.kotest:kotest-runner-junit5-jvm:4.1.0

[sam]

You'll need io.kotestkotest runner console jvm4.1.0 as well

[sam]

but that shouldn't stop the icons from appearing though

[xenomachina]

I added testImplementation "io.kotest:kotest-runner-console-jvm:4.1.0" to my dependencies, and reimported gradle in IJ, but still don't see any play icons. Where should they be?

[xenomachina]

I looked at the one where it was working, and I see what you mean by play icons. Yeah, they don't show up when we're using 4.1.0.

[xenomachina]

I just tried an intermediate version of our code, where we first switched from kotlintest to kotest, and that works. That was 4.0.6. Going to see if I can pinpoint exactly where it stopped working...

[sam]

Ok thanks

[xenomachina]

So far it's looking like it stopped showing the run and debug options on specs right when we moved from kotest 4.0.7 to kotest 4.1.0.

[xenomachina]

Yes, if I checkout the earliest version where it doesn't work, and change the kotest version back to 4.0.7 I start getting run+debug options on specs in IntelliJ, but if I change the version back to 4.1.0 then run+debug disappear from specs.

[sam]

Which version of intellij

[xenomachina]

2020.1.1 CE

[johnaqel]

Same happened for me when I upgraded kotest to 4.1.0. Running on Ultimate 2020.1.

[simon.vergauwen]

@sam just to let you know. I’m still seeing a lot of weird behavior as well in 4.1.0, that I didn’t see with plugin 0.9.3 and 4.0.6.

[sam]

The plugin shouldn't have even worked with 4.0.6 at all. If you were clicking the green run icon on the classname then that was coming from junit.

[simon.vergauwen]

Also plugin 0.9.3 from before the official plugin release? 😮

[sam]

Yep

[simon.vergauwen]

Strange. That worked great for me.. 😅

[sam]

The plugin was always designed for 4.1 snapshots

[sam]

It needed classes that weren't in 4.0.x

[sam]

The run icon at the class level?

[simon.vergauwen]

I’m seeing a lot of weird things with 4.1.0 and the plugin. Just did a reboot, updated of IDEA, invalidate & restart caches, and re-import Gradle.
And ended up here again. https://kotlinlang.slack.com/archives/CT0G9SD7Z/p1593071281019200

[simon.vergauwen]

I even cleaned up old IDEA folders 😕

[sam]

Before you upgraded where was the run icon

[simon.vergauwen]

On individual tests and on the class

[simon.vergauwen]

Sorry not 0.9.3

kotest-plugin-intellij-0.90.16.zip

[simon.vergauwen]

That’s the latest one I can find in my downloads folder, so that must be the one I was using before upgrading.

[sam]

Right. And now you don't see the icons at all.

[simon.vergauwen]

I see icons everywhere, but can’t run anything after restart/reset. And earlier it wasn’t properly rebuilding and never picked up any new changes.

[simon.vergauwen]

(CLI worked fine)

[sam]

Can you create an issue and paste in a screen shot of the run config that's created when you try to run a nested test

[simon.vergauwen]

Alright, will do 👍

[sam]

And also run with env var KOTEST_DEBUG=true

[simon.vergauwen]

👍

[sam]

And add std out to the issue

[sam]

Finally paste in the exact intellij version from the about box

[sam]

I'll match the version. I'm on linux though

[simon.vergauwen]

@sam sad to report back it’s flaky.
When I was trying to run with KOTEST_DEBUG=true, after I did my own series of rebooting/restarting/invalidating caches/re-importing it seemed to work again yesterday.

If I can figure out a more reliable/reproduce-able scenario then I’ll create a ticket with the suggested scenarios.

[simon.vergauwen]

Sorry I am unable to provide more info atm 😕

[sam]

The log itself will be useful to me

[simon.vergauwen]

I just got an update of the plugin. Was that related to this? Can I follow the changes of the plugin somewhere?

[sam]

There were a couple of bugs fixed but I don't think anything related to this

[simon.vergauwen]

Encountered it again today on a fresh instal of IntelliJ Ultimate.
https://github.com/kotest/kotest/issues/1542