Repository navigation
Since version 1.48.0: The test run did not record any output #4260
Description
I reported the problem here microsoft/vscode-java-test#1814
However, the problem is caused by this extension.
When running tests, nothing is really executed with a message in "Test Results"
The test run did not record any output.
This is a Maven project, which has always worked before.
I've also tried with other Maven projects with the same result.
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...
1.49.0 does not solve the problem.
The only solution is to revert to 1.47.0
Activity
fbricon commentedon Nov 20, 2025
For now the fix is available in the vscode-java 1.50 pre-release.
LorenzoBettini commentedon Nov 20, 2025
I confirm that 1.50.2025112008 fixes the problem! :)
LorenzoBettini commentedon Nov 26, 2025
@fbricon you closed this, but the fixed version hasn't been released yet, has it?
Only the pre-release version works.
fbricon commentedon Nov 26, 2025
will be released later today
fbricon commentedon Nov 26, 2025
1.50 is now available on the marketplaces
Conflict between JUnit 5 and JUnit 6 tests
tot121212 commentedon Jan 28, 2026
I am getting this error currently on 1.51. Maybe wasn't fixed yet or was reintroduced?
tot121212 commentedon Jan 28, 2026
Switching to pre-release seemed to fix.
camel-eon commentedon Apr 15, 2026
Unfortunately this still happens even on the latest pre-release versions of the relevant extensions. Downgrading this to 1.47.0, test runner to 0.43.2 and project manager to 0.26 and debugger to 0.59 fixed it...
I had this issue even without Maven, an empty unmanaged project with "Enable Java Tests" -> "JUnit Jupiter" and a basic test file already cause this problem (while running the tests manually from the command line by invoking the JUnit JAR works fine).