Sheng Chen

Results 704 comments of Sheng Chen

@Empressia thank you for reporting the issue. Would you mind to update it to English?

Thank you @Empressia, will take a look

@Empressia Please correct me if I'm wrong. The sample project looks very similar with that in https://github.com/microsoft/vscode-java-test/issues/1101. So I guess once the user can set `modulePaths` in the test configuration,...

We planed to add `modulePath` field in the test configuration in the next release. Since this issue looks similar to #1101, I'm closing this one and use #1101 to track...

What's the version of `Language Support for Java` extension on your side? The sample project https://github.com/Empressia/VSCodeJavaTest02 works on my side without any additional settings: ![image](https://user-images.githubusercontent.com/6193897/147306234-ef00777b-2fde-4f41-bb8a-2123e1d80802.png)

Looks like a issue related to the file system. Have you tried it in Eclipse?

Yes I can repro this issue but have no idea why. The debug console says: ``` ... at java.base/java.lang.Class.newInstance(Class.java:584) Class.java:584 at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.createRawTestLoader(RemoteTestRunner.java:371) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.createLoader(RemoteTestRunner.java:366) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.defaultInit(RemoteTestRunner.java:310) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.init(RemoteTestRunner.java:225) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)...

Thank you for the information. I added a breakpoint at https://github.com/microsoft/vscode-java-test/blob/78717ac77a2168372d6109d6fad82ad439e93900/src/controller/testController.ts#L229 And below is the configuration that test runner will pass to the debugger ```js { name: "Launch Java Tests...

This issue will be addressed in `0.15.0` We refactored the logic of parsing the test results recently.

@Sunnyxpected We have limited support for this scenario, but if you trigger the tests at the inherited class, the methods from the super class should also get run and appear...