Repository navigation
Can't run or debug JUnit 5 from secondary class #859
Description
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:
- Open the JUnit5 project in VSCode: https://github.com/ZhengJun003/junit5-samples/tree/testrunner
- Run
MyFastTestITandTestTemplateIin the test explorer
Result:
Added by Sheng Chen (@jdneo)
❗️Solution for those people who cannot run JUnit 5 from the Invisible project(dependency managed in lib folder)
Activity
ZhengJun003 commentedon Oct 29, 2019
Java file's name and class name must be the same, otherwise, maven will skip these cases
jdneo commentedon Oct 30, 2019
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
[-]Can't run or debug junit5 'TestTemplate' and 'Meta Annotation' case[/-][+]Can't run or debug junit5 from secondary class[/+][-]Can't run or debug junit5 from secondary class[/-][+]Can't run or debug JUnit 5 from secondary class[/+]geist-2501 commentedon Nov 2, 2019
ZhengJun003 commentedon Nov 4, 2019
geist-2501 commentedon Nov 5, 2019
jdneo commentedon Nov 6, 2019
geist-2501 commentedon Nov 6, 2019
OneBigOwnage commentedon Nov 10, 2019
jdneo commentedon Nov 11, 2019
rajkundu commentedon Nov 11, 2019
jdneo commentedon Nov 11, 2019
geist-2501 commentedon Nov 11, 2019
jdneo commentedon Nov 11, 2019
Ok so here is the solution for those people who cannot run JUnit 5 from the Invisible project(dependency managed in
libfolder):libfoldervwxyzjn commentedon Nov 19, 2019
Sheng Chen (@jdneo) Thanks that works!
moinessim commentedon Nov 20, 2019
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 commentedon Nov 20, 2019
moinessim Have you tried this solution?
moinessim commentedon Feb 27, 2020
Hi Sheng Chen (@jdneo), I tried the following, but had the same error message.
Adding the Junit Standalone Console jar:
github-actions commentedon Nov 12, 2025
Hi ZhengJun003, 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.
No known workaround exists for the “Failed to parse the JUnit launch arguments” error in the current Java Test Runner releases. Please try the following:
Developer: Clean Java Language Server Workspace) and restart.If the issue persists, file a new issue with full logs from the “Java Test Runner” output channel.
Other references with low confidence
Some tests inside static class won't run after click "Run All Tests" button #1283 – Some tests inside static class won’t run
Similar JUnit-5 test discovery/runtime issue in
testrunnerbranch. No parse-error solution.Some tests inside static class won't run after click "Run All Tests" button #1283
Failed to run invisible test project #808 – Failed to run invisible test project
Tests stuck/running status when dependencies are in a
lib/folder. Different error but similar troubleshooting pattern.Failed to run invisible test project #808
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!