You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you create an option in the IDE to define the JDK location on a computer?
I have several JDK on my computer, gradle can find them and in a previous version of the plugin, I started my test with Gradle (because Kotest is not able to find my JDK)
However, since the last update of the plugin (1.3.72-IC-2023.2) on my IDE 2023.2.5, Kotest is always running when I want to start test execution for a file. The problem is that Kotest cannot find any of my JDK. So, it's impossible to run tests with Gradle (because Kotest take the lead) or with Kotest (because he cannot find my JDK)
Intellij Ultimate: 2023.2.5
Kotest-plugin: 1.3.72-IC-2023.2
Kotest: 5.8.0
Previous plugin (with which I could launch my tests with Gradle): 1.3.71-IC-2023.2
Workaround:
To run a test file with Gradle, create a custom configuration with these values (for JVM test): :cleanJvmTest :jvmTest --tests "package.classname"
Can you create an option in the IDE to define the JDK location on a computer?
I have several JDK on my computer, gradle can find them and in a previous version of the plugin, I started my test with Gradle (because Kotest is not able to find my JDK)
However, since the last update of the plugin (1.3.72-IC-2023.2) on my IDE 2023.2.5, Kotest is always running when I want to start test execution for a file. The problem is that Kotest cannot find any of my JDK. So, it's impossible to run tests with Gradle (because Kotest take the lead) or with Kotest (because he cannot find my JDK)
Intellij Ultimate: 2023.2.5
Kotest-plugin: 1.3.72-IC-2023.2
Kotest: 5.8.0
Previous plugin (with which I could launch my tests with Gradle): 1.3.71-IC-2023.2
We cannot download a previous version on the plugin site https://plugins.jetbrains.com/plugin/14080-kotest/versions/stable
The text was updated successfully, but these errors were encountered: