Quarkus junit tests don't work

[l0co]

One cannot run unit/integration tests with Quarkus > 3.22. Please compare with:

1. Non-viable test classloader when running a group of tests (Class or Package) in VSCode quarkusio/quarkus#48014 (comment)
2. Unable to run QuarkusTests in Eclipse since Quarkus 3.22 quarkusio/quarkus#47656
3. https://quarkus.io/blog/test-classloading-rewrite/

It looks like, the fix has been applied in eclipse runner, but has not been applied for the VSCode extenstion, which is still from Apr 03 2025. I think you have to upgrade dependency org.eclipse.jdt.junit5.runtime_1.1.300.v20231214-1952.jar which seems to very old (2023?) to org.eclipse.jdt.junit5.runtime-1.1.400.jar, plus all related dependencies.

[github-actions]

Hi Lukasz Frankowski (@l0co), 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.

Workaround

• Manually upgrade the JDT JUnit5 runtime shipped with the VS Code Java Test extension:
  1. Download org.eclipse.jdt.junit5.runtime-1.1.400.jar from https://download.eclipse.org/jdt/junit/updates/download/release/1.1.400/
  2. Locate your extension folder (e.g. ~/.vscode/extensions/vscjava.vscode-java-test-<version>/server/) and replace org.eclipse.jdt.junit5.runtime_1.1.300.v20231214-1952.jar.
  3. Reload VS Code.

Track upstream fix: once the extension updates its org.eclipse.jdt.junit5.runtime dependency, you can revert to the official release.

Relevant references

• Non-viable test classloader when running a group of tests (Class or Package) in VSCode quarkusio/quarkus#48014: fix applied in Eclipse runner → Non-viable test classloader when running a group of tests (Class or Package) in VSCode quarkusio/quarkus#48014 (comment)
• Unable to run QuarkusTests in Eclipse since Quarkus 3.22 quarkusio/quarkus#47656: classloading issues after test rewrite → Unable to run QuarkusTests in Eclipse since Quarkus 3.22 quarkusio/quarkus#47656
• Quarkus blog “Test classloading rewrite” → https://quarkus.io/blog/test-classloading-rewrite/

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!

[holly-cummins]

As Lukasz Frankowski (@l0co) says, the fix for this is eclipse-jdt/eclipse.jdt.ui#2258. It doesn't seem to have made it into the runner extension yet, which isn't surprising, since the last update of the runner extension was seven months ago.

I've tried the suggested workaround. I had to pull the jdt jar from a complete installation, because the url was a 404. Even with that adjustment, I get "no tests found" after patching. Adjusting the jar reference the package.json in the extension doesn't help. However, others report it does work: quarkusio/quarkus#48014 (comment)

[mdima]

Hello, this fix would be awesome. Thanks!

[maxandersen]

Fred Bricon (@fbricon) or Roland Grunberg (@rgrunber) can you help here? this is quite annoying that the vscode-test is using older eclipse which then breaks proper tests :/

[fbricon]

JUnit runtimes need to be updated in this extension, notably for JUnit 6 support, so it should be addressed soon(TM), either by wenyt (@wenytang-ms) Changyong Gong (@chagong) or Snjeza (@snjeza)

[snjeza]

This is an upstream jdt.ui issue. I have created eclipse-jdt/eclipse.jdt.ui#2654