All my issues above have been quickly fixed so I’m hoping for this last one to be as quick to solve ...

# kotest

[mboudraa]

All my issues above have been quickly fixed so I’m hoping for this last one to be as quick to solve 🙂

The last problem, I’m facing is whenever I change a test or add a test in Android Studio, the runner runs the test as if they didnt change.
I have to rebuild the module everytime for the change to have an effect.

Is there a specific configuration or a plugin besides the intelliJ one that I should add to make things work mor smoothly?

FYI im on AS 4.2 beta3 and writing my tests in a multiplatform module

[sam]

With the caveat I don't use AS, is there an option to choose the "runner" for tests like intellij has? Where you can flip between gradle and intellij.

[sam]

[mboudraa]

We don’t have that option. AS automatically uses gradle as a way to build the project

[sam]

When you run, do you see gradle running in the intellij console?

[sam]

And do you see the build task being triggered

[mboudraa]

with kotest it doesnt feel like it no

[mboudraa]

Especially since I can see that happening in the test window:
/Library/Java/JavaVirtualMachines/adoptopenjdk-15.jdk/Contents/Home/bin/java -Didea.test.cyclic.buffer.size=1048576 -javaagent:/Users/mounir/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7033425/Android Studio 4.2...

[mboudraa]

which makes me think that it runs the test using intelliJ and not gradle.

[sam]

right, and maybe that's not triggering the build part in AS

[mboudraa]

¯\_(ツ)_/¯

[mboudraa]

Should I use
https://github.com/kotest/kotest-gradle-plugin

[sam]

no, that's for JVM only

[sam]

what version of AS ?

[mboudraa]

4.2 beta 3

[sam]

Something may have changed

[mboudraa]

I have the plugin 1.1.24-IC-2020.2

[mboudraa]

I believe because AS 4.2 is based on 2020.2