JUnit 5 error message on project that uses JUnit 6

[MaddyGuthridge]

When I attempt to use VS Code to run my project's test suite, I get the following error:

Cannot find org.junit.platform.commons.annotation.Testable on project build path. JUnit 5 tests can only be run if JUnit 5 is on the build path.

This is very unusual, given that the project uses JUnit 6, as per the build.gradle:

dependencies {
    // Use JUnit Jupiter for testing.
    testImplementation 'org.junit.jupiter:junit-jupiter:6.0.1'
    //                                                  ^^^^^
    testRuntimeOnly 'org.junit.platform:junit-platform-launcher'
}

I have confirmed that tests run correctly when using gradle test.

I am currently making a minimal reproduction repo, which I will link here as soon as it is completed.

[github-actions]

Hi @MaddyGuthridge, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Solution

• Add the missing JUnit Platform Commons dependency to your Gradle build so VS Code can locate org.junit.platform.commons.annotation.Testable:

  dependencies {
    testImplementation 'org.junit.jupiter:junit-jupiter:6.0.1'
    testImplementation 'org.junit.platform:junit-platform-commons:1.10.1'   // match the platform version
    testRuntimeOnly   'org.junit.platform:junit-platform-launcher:1.10.1'
  }

Duplicate Issue

• This is the same root cause as
  • Tests cannot be launched: add org.junit.platform:junit-platform-commons
    • Tests cannot be launched #1481 (comment)

Other references worth checking

• Missing compatibility with JUnit 5.4.0+ (add junit-platform-commons:1.4.0)
  • Missing compatibility with Junit 5.4.0+ #764 (comment)

• NoClassDefFoundError when running JUnit5 tests (workarounds: upgrade Jupiter, add launcher)
  • NoClassDefFoundError when running JUnit5 tests #971 (comment)

Other references with low confidence

- (none)

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

[MaddyGuthridge]

Dear AI, you are wrong. Adding the additional dependency did not help. The Java Test Runner extension still searches for JUnit 5 despite this project using JUnit 6.

To the maintainers of this repository, I deeply question your decision to implement this AI system. It has closed this issue as a duplicate of another issue without first verifying this fact. Even after giving a 👎 reaction to the comment, the issue remains closed, with no obvious way to get it reopened. This is an awful experience which gives me very little faith that my issue will ever receive a human review. I completely understand the desire to automatically resolve low-quality issues with simple AI assistance, but your system is clearly catching legitimate issues in the crossfire. Maybe this bug is a skill issue on my part, but your AI slop hallucinations certainly did not help me find the solution. I implore you to rethink the implementation of this "feature". Closing legitimate issues at the behest of an unreliable AI with no human review is exactly how Microsoft is earning their name "Microslop".

[chagong]

Thanks, @MaddyGuthridge for reporting the issue and share your feedback for triage bot. We will investigate the issue and improve our triage bot.