Can't run or debug JUnit 5 from secondary class

[ZhengJun003]

Environment:

OS: Windows
JDK: 8/12
Java Extensions:

• Language Support for Java(TM) by Red Hat： 0.52.0
• Debugger for Java: 0.23.0
• Java Test Runner: 0.21.0

Steps to reproduce:

1. Open the JUnit5 project in VSCode: https://github.com/ZhengJun003/junit5-samples/tree/testrunner
2. Run MyFastTestIT and TestTemplateI in the test explorer

Result:

---

Added by @jdneo
❗️Solution for those people who cannot run JUnit 5 from the Invisible project(dependency managed in lib folder)

[ZhengJun003]

Java file's name and class name must be the same, otherwise, maven will skip these cases

[jdneo]

So it turns out that this is an Eclipse side bug. It will happen when running a class name which is different from the compilation unit name.

I'll reopen it until we fix it in the upstream.

See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=529722#c1

[jdneo]

Ok so here is the solution for those people who cannot run JUnit 5 from the Invisible project(dependency managed in lib folder):

1. Update VS Code to 1.40.0
2. Update Test Runner to 0.21.0
3. Have the Junit Standalone Console jar in a lib folder

Note: You may still cannot run JUnit 5 test if your class name is not the same as the Java file. This is a bug from the upstream Eclipse side.

[vwxyzjn]

@jdneo Thanks that works!

[moinessim]

Had the same problem, read this rolled back to v0.20.0 and it worked.
I have last version of vscode and class names equal file names.
Didn't try having the console jar in a lib folder. I'm using Maven. Don't want to save jars in source control.

[jdneo]

@moinessim Have you tried this solution?

[moinessim]

@moinessim Have you tried this solution?

Hi @jdneo, I tried the following, but had the same error message.
Adding the Junit Standalone Console jar:

• in a lib folder in the project root directory.
• in a lib folder next to the test class.
• in the pom.xml as a Maven dependency with test scope.