@dbalek

vscode-java-test-0.40.2023092502.vsix.zip

Using this private build and the latest Pre-release of the vscode-gradle extension, which uses the build server approach should solve the problem. I tested it locally on my machine and it works.

As it is mentioned in #1608, bump to JUnit 5.10.0 might cause the projects using <= 5.9.x failed to run the tests. I'm not planning to do that at this moment.

From your side, is there any kind of due date or something that need the VS Code Java side to address this issue ASAP? If yes, please let me know.

Unfortunatly, tested with the attached vscode-java-test extension and the pre-release (v3.12.2023091801) of the vscode-gradle extension I am still getting the same error as in #1613

Sorry forget to mention, you need to clean the workspace cache.

• Open the command palette (Press F1)
• Select Java: Clean Java Language Server Workspace > Reload and delete

Cleaning the workspace cache, still the same result

Could you share your VS Code settings? And maybe a screenshot of the Java Projects View (F1 >View: Focus on Java Projects View)

Another difference is that I'm using Micronaut 4.1.2 instead of 4.1.1

I have started VSCode with the fresh --user-data-dir and --extensions-dir, and I have created the new Micronaut 4.1.2 project. So, the settings.json is almost empty now:

{
    "workbench.startupEditor": "none"
}

Still the same result:

There is a node named Project and External Dependencies in the Java Projects View, which is a hint that the Gradle project is still imported by the old Gradle importer.

Could you try to clean Java Language Server Workspace again?

More details, see: redhat-developer/vscode-java#3260 (comment). Sorry for the confusion here.

The node is named Referenced Libraries (Read-only) now, otherwise no change...

Still failed to launch tests?

Yes, exactly the same error.

I can reproduce it now on MacOS. Previously I was using Windows, which works fine.

Is still open? Do you need help?

Thank you @yanisderbikov. Since bumping to JUnit 5.10.0 might cause the projects using <= 5.9.x failed to run the tests. I'm not planning to do that at this moment.

More and more users are migrating to 5.10.x

The estimate time for updating the target platform will happen in May.

Fixed in #1722