Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Test Framework quit unexpectedly" error running ignored test #251

Open
ShindongLee opened this issue Apr 12, 2023 · 2 comments
Open

"Test Framework quit unexpectedly" error running ignored test #251

ShindongLee opened this issue Apr 12, 2023 · 2 comments
Labels
bug Something isn't working wontfix This will not be worked on

Comments

@ShindongLee
Copy link

Kotlin 1.8.20
Kotest 5.5.5

sc 138

@Ignored
class SampleTest: FreeSpec({
    "test" {
        println("test")
    }
})

In earlier versions, it was possible to run a specific test in Kotest by clicking the '>' button next to the test name, even if the corresponding spec was ignored. This was very useful when wanting to run a test in the IDE, but not wanting to run it every time for CI.

sc 137

However, with the current version, running a single test using the '>' button results in a "Test Framework quit unexpectedly" error. It is not clear whether this is an issue with Kotest or with its IntelliJ plugin.

@LeoColman LeoColman transferred this issue from kotest/kotest Apr 25, 2023
@LeoColman LeoColman added the bug Something isn't working label Apr 25, 2023
@stale
Copy link

stale bot commented Aug 13, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Aug 13, 2023
@Tomasz-Marciniak
Copy link

Tomasz-Marciniak commented Jun 10, 2024

@ShindongLee - Intellij kotest plugin runs a single test with pure Java command. In my case the test was simply not found because I used @tags and @RequiresTag annotation so to fix it I had to add the tag to execution configuration.

  1. Open run configuration which is failing
  2. Click modify option
  3. Add "add vm options"
  4. -Dkotest.tags="myTag"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants