IntelliJ Gradle Testing Support
See original GitHub issuekotest version 4.2.3. Latest version of IntelliJ IDEA CE.
I just recently updated to kotest from kotlintest. In the past, IntelliJ was able to at least identify entire kotlintest StringSpec
blocks as tests. You could then use f:
focusing to pick out individual tests to run, even if (IIRC) IntelliJ couldn’t identify individual tests within the spec.
Since the upgrade to kotest
there is no option to run tests. I have tried the kotest
plugin, but it doesn’t seem to honor my settings to run tests with Gradle, which I’d like to continue doing so that I don’t need to duplicate test configurations in two places.
Is this the expected behavior—or a bug with the kotest
IntelliJ plugin, or something wonky about my environment? Unfortunately this represents a fairly serious regression for our use case, since our project has a large number of tests and the entire suite runs quite slowly.
Issue Analytics
- State:
- Created 3 years ago
- Comments:22 (12 by maintainers)
Top GitHub Comments
What’s the status on this? I’m using the kotest intellij plugin
1.1.24-IC-2020.3
and I cannot get idea to run the tests with gradle. The “run tests using” option is set to gradle, and I’ve tried deleting the test configurations, but no luck so far.Edit: so running the entire spec class seems to work and uses gradle. It’s running one of the nested tests that doesn’t use gradle as expected (I am using FreeSpec). Is this a known limitation of the current implementation - that running an entire spec with gradle is possible, but running one of the nested tests is not?
How are you getting on with the new build @gchallen ?