The test run did not record any output.

[LorenzoBettini]

As of today, with version 0.43.2, when running tests, nothing is really executed with a message in "Test Results"

The test run did not record any output.

Reverting to the previous version just doesn't work: no tests are detected at all, asking me to install (update) the extension.

[github-actions[bot]]

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

• Try clearing the Test Results panel before rerunning: click the trash icon in the Test Results view, then rerun your tests. This matches the workaround in issue #1618 (ref: https://github.com/microsoft/vscode-java-test/issues/1618) • Open the “Java Test” output channel (View → Output, then select “Java Test”) to see detailed parsing logs or errors. • Uninstall and reinstall the Java Test Runner extension, then reload VS Code. • If tests still aren’t detected, make sure your project is correctly configured for Maven/Gradle and you’re using a supported JUnit version. • (Optional) Enable debug logging via setting java.test.logLevel to debug, rerun tests, and share the logs for further diagnosis.

Other references with low confidence

• Issue #258 “Make runner better consume test output”: discusses shortcomings in how test output is parsed but has no direct fix. https://github.com/microsoft/vscode-java-test/issues/258

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!

[LorenzoBettini]

I forgot to mention: this is a Maven project, which has always worked before. I've also tried with other Maven projects with the same result.

[LorenzoBettini]

This is the curlprit in this updated version 1.48.0: before the restart of the updated extensions it used to work, afterward it shows the problem above.

[LorenzoBettini]

Moreover, I see no "Trash Icon" to clear the results, neither in the "TESTING" panel nor in the "TEST RESULTS" view.

However, no I note an error popping up:

"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."

In my POM I have

   <properties>
        <junit-jupiter.version>6.0.0</junit-jupiter.version>
    </properties>

	<dependencyManagement>
		<dependencies>
			<dependency>
				<groupId>org.junit</groupId>
				<artifactId>junit-bom</artifactId>
				<version>${junit-jupiter.version}</version>
				<type>pom</type>
				<scope>import</scope>
			</dependency>
        </dependencies>
    </dependencyManagement>

    <dependencies>
        <dependency>
			<groupId>org.junit.jupiter</groupId>
			<artifactId>junit-jupiter-api</artifactId>
			<scope>test</scope>
		</dependency>
    </dependencies>

So I do have JUnit in my build path...

[LorenzoBettini]

I confirm: 1.47.0 of "redhat.java" works, 1.48.0 doesn't.

[tzolov]

I confirm: 1.47.0 of "redhat.java" works, 1.48.0 doesn't.

Reverting to 1.47.0 resolved the issue to me as well. Thanks @LorenzoBettini

[LorenzoBettini]

They've just released 1.49.0 with the same problem!

[rgrunber]

Do you have a sample project that can be shared ?

I tried with vscode-java 1.49.0 & vscode-java-test 0.43.2. It works for me.

[snjeza]

I can reproduce the issue with Test Runner for Java pre-release 0.43,2025040304. This is an old version and is not compatible with VS Code LS >= 1.48.0 @LorenzoBettini @tzolov Can you try installing Test Runner For Java 0.43.2 and disable Auto Update?

[fbricon]

So the problem is due to jdt.ls bringing in new versions of eclipse junit support, which now requires vscode-java-test to ship junit6 specific bundles. So the proper fix would be a new release of vscode-java-test including those junit6 support jars.

Now depending on the time it'll take for the team to find a fix (@snjeza is looking into it) and then performing another vscode-java-test release, we can probably do another vscode-java release (1.50) where we surgically rollback the eclipse junit support to the one used in vscode-java 1.47. @testforstephen wdyt?

[LorenzoBettini]

Hi, sorry for being late; so, for the moment, what should I try?

"installing Test Runner For Java 0.43.2 and disable Auto Update?"

or wait for 1.50.

For the moment, holding 1.47.0 of "redhat.java" allows me to work anyway.

[fbricon]

@LorenzoBettini stick to 1.47 for now. We'll either have a new vscode-java release or pre-release restoring JUnit 6 support today hopefully, by Monday at the latest.

[fbricon]

Please test the latest vscode-java 1.50 pre-release

[LorenzoBettini]

As commented here https://github.com/redhat-developer/vscode-java/issues/4260#issuecomment-3557850209 it does fix it, thanks!

[chagong]

So the problem is due to jdt.ls bringing in new versions of eclipse junit support, which now requires vscode-java-test to ship junit6 specific bundles. So the proper fix would be a new release of vscode-java-test including those junit6 support jars.

Now depending on the time it'll take for the team to find a fix (@snjeza is looking into it) and then performing another vscode-java-test release, we can probably do another vscode-java release (1.50) where we surgically rollback the eclipse junit support to the one used in vscode-java 1.47. @testforstephen wdyt?

@fbricon do we need to upgrade all JUNIT bundles to latest in jdtls.ext for vscode-java-test? And a cooperative work for jdtls and vscode-java-test?

[snjeza]

@fbricon @chagong @testforstephen You may want to take a look at https://github.com/eclipse-jdt/eclipse.jdt.ui/issues/2654