Test Runner for Java Extension downloads old JUnit standalone

[joaocaram]

When we create a "no build tools" Java project and, after that, try to "Enable Java Tests" using the "test icon", it downloads the "junit-platform-console-standalone-1.13.0-M3.jar" file instead of JUnit 6 versions. This old version is not working with most recent Test Runner and Language Support for Java Extensions. (i'm using Extension Pack for Java 0.31.0, Language Support 1.54.0 and Test Runner 0.45.0).

I know we can fix it by manually downloading more recent standalones, or creating Maven/Gradle projects. But when the platform is being used to teach some dozen first-term students, creating a Maven project, keep in mind the directories and packages structure etc are annoying and time consuming distractions.

Besides, if there is a plugin to make things easier for everyone (such as downloading and including the reference to the Junit jar), it should work properly. So, please, take a few minutes to fix this.

[github-actions]

Hi @joaocaram, 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.

Suggestions

• Use a build tool (Maven/Gradle) project so that test dependencies are declared in your pom.xml/build.gradle instead of relying on the standalone JAR download.
• As a temporary workaround, manually download a newer junit-platform-console-standalone JAR (e.g. v1.9.2) from https://repo1.maven.org/maven2/org/junit/platform/junit-platform-console-standalone/ and replace the junit-platform-console-standalone-1.13.0-M3.jar in your project’s lib folder.
• Upvote or comment on the existing feature request to bump the default standalone JAR version in the Test Runner extension so the next release ships a recent JUnit platform.

References

• VS Java Test extension is unable to detect JUnit tests (#1498) – explains the “Enable Java Tests” workflow for no-build-tools projects and how the extension downloads the standalone JAR.

No duplicates found.

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!

[joaocaram]

Hi AI/bot @github-actions

* Upvote or comment on the existing feature request to bump the default standalone JAR version in the Test Runner extension so the next release ships a recent JUnit platform.

Sorry, I may be missing something here. Where do I find the feature request so I can upvote?

Thanks