Single File Test Support

[praenubilus]

The plugin currently requires a maven/gradle project to run the unit tests which does not make sense.

1. The debugger support single non project file run/debug.
2. Individual file test works smoothly for python, so I hope the java test runner can also run like that, even all output is just in console.

Is there a timeline for when single/individual file unit test running will be supported?

[jdneo]

So the workflow might be:

1. The user creates a single java file
2. The user adds dependencies (e.g. JUnit) into the single-file project
3. After the project is set up correctly, the user can write some test cases and run the tests

@praenubilus Is this the workflow you want to have to support single file test?

[praenubilus]

So the workflow might be:

1. The user creates a single java file
2. The user adds dependencies (e.g. JUnit) into the single-file project
3. After the project is set up correctly, the user can write some test cases and run the tests

@praenubilus Is this the workflow you want to have to support single file test?

That looks good. But is there a way to put the dependency into the settings.json? In python plugin, you can configure which test framework you want to use for the workspace, and their path(pytest, unittest etc). I guess the best way here is add a test framework configuration in settings, let user to choose (JUnit, TestNG or other test framework), configure the dependencies path. The setting works either for users or workspace.

[jdneo]

@praenubilus The way to manage the dependency in single-file project is worth discussing. Actually, this is a common problem that needs to be solved. I created an issue here: microsoft/vscode-java-dependency#76. Hopefully, this can be achieved after the dependency extension supports this.

[jdneo]

Now the Java Language Server supports to manage the dependencies into the lib folder, this does not need the user to have building tools like Maven or Gradle in their project. See: redhat-developer/vscode-java#501 (comment)

I will start to investigate how to support this kind of project in the Test Runner and unblock those kinds of users.

[praenubilus]

I hope you can let the plugin configure a universal default lib/jar path, that means if the user does not explicitly configure a custom lib, jars, classes under that path will always being included by default. Then we can put some default framework jar files under that lib.
Another idea is, let the user to specify a testing library path globally/workspace-wise, it can be junit/test-ng and extra test libraries if necesary(e.g. assertj)

[jdneo]

Thank you @praenubilus. About the default lib path, this could be a feature request for https://github.com/eclipse/eclipse.jdt.ls, which is also known as the Java Language Server.

And for the testing lib path, I'll consider it. Thank you.