Repository navigation
Quarkus junit tests don't work #1800
Description
One cannot run unit/integration tests with Quarkus > 3.22. Please compare with:
- 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
- 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.
Activity
github-actions commentedon Oct 15, 2025
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
~/.vscode/extensions/vscjava.vscode-java-test-<version>/server/) and replaceorg.eclipse.jdt.junit5.runtime_1.1.300.v20231214-1952.jar.Track upstream fix: once the extension updates its
org.eclipse.jdt.junit5.runtimedependency, you can revert to the official release.Relevant references
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 commentedon Oct 30, 2025
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.jsonin the extension doesn't help. However, others report it does work: quarkusio/quarkus#48014 (comment)mdima commentedon Nov 5, 2025
Hello, this fix would be awesome. Thanks!
maxandersen commentedon Nov 20, 2025
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 commentedon Nov 20, 2025
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 commentedon Nov 20, 2025
This is an upstream jdt.ui issue. I have created eclipse-jdt/eclipse.jdt.ui#2654
Conflict between JUnit 5 and JUnit 6 tests