You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Versions 1.54 and 1.55 break Test Runner for Java extension latest version (0.45.0) #4437
Describe the bug
A clear and concise description of what the problem is.
This extension (versions 1.54 and 1.55) causes Java Test Runner extension not to detect and Java Unit Tests
To Reproduce
Steps to reproduce the behavior:
Install 1.54 or 1.55
Install Test Runner For Java (latest version - 0.45.0)
If codebase contains unit test files, testing page will be empty (could not find any tests) and Test classes won't have run buttons.
[Please attach a sample project reproducing the error]
[Please attach logs. See https://github.com/redhat-developer/vscode-java/wiki/Troubleshooting#enable-logging]
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
This should be fixed by Test Runner for Java 0.46.0. Please update Test Runner for Java to 0.46.0 or newer together with redhat.java1.55.0 or newer.
I verified this combination with a plain Eclipse Java project using junit-platform-console-standalone-1.13.4.jar: tests are discovered correctly and classified as JUnit 5.
This fix works. Just to take into account, if you are using VScodium with a non Microsoft marketplace the last version of the Test runner is 0.45 BUT the Language Support for Java(TM) by Red Hat is the last one (1.55.0). So you must update the Java Test runner version manually or just revert to the previous version and wait until both are updated.
@datho7561 This has been fixed in Test Runner for Java 0.46.0. The reporter's scenario works with redhat.java1.55.0 or newer together with vscjava.vscode-java-test0.46.0 or newer, and another user has confirmed the fix as well.
The remaining concern mentioned above was that some non-Microsoft marketplaces, such as Open VSX, were still serving Test Runner 0.45.0; users on those marketplaces need to update the test extension manually or temporarily roll back redhat.java until both versions are available.
Activity
wenytang-ms commentedon Jun 26, 2026
@nathanielfinkgapmaps Thanks for reporting this.
This should be fixed by Test Runner for Java
0.46.0. Please update Test Runner for Java to0.46.0or newer together withredhat.java1.55.0or newer.I verified this combination with a plain Eclipse Java project using
junit-platform-console-standalone-1.13.4.jar: tests are discovered correctly and classified as JUnit 5.albertodlc commentedon Jun 30, 2026
This fix works. Just to take into account, if you are using VScodium with a non Microsoft marketplace the last version of the Test runner is 0.45 BUT the
Language Support for Java(TM) by Red Hatis the last one (1.55.0). So you must update the Java Test runner version manually or just revert to the previous version and wait until both are updated.mdakash472452-afk commentedon Jul 8, 2026
mdakash472452-afk commentedon Jul 8, 2026
wenytang-ms commentedon Sep 4, 2026
@datho7561 This has been fixed in Test Runner for Java
0.46.0. The reporter's scenario works withredhat.java1.55.0or newer together withvscjava.vscode-java-test0.46.0or newer, and another user has confirmed the fix as well.The remaining concern mentioned above was that some non-Microsoft marketplaces, such as Open VSX, were still serving Test Runner
0.45.0; users on those marketplaces need to update the test extension manually or temporarily roll backredhat.javauntil both versions are available.I think we can close this issue as completed.