Currently, we force showing output window whenever users run test cases. This could be disruptive when users are currently working on debug console or integrated terminal.

We can provide an option in user settings to allow switch that behavior on and off.

We have three type of events: run test, debug test, show details. right now only perf data contains eventid, we'd better pass eventid into all the err/info logs that are recorded in the session of event.

Test logs should be able to be closed without asking users to save the logs.

This can be achieved by using the DocumentContentProvider API.

As the java community progresses to use JUnit 5 instead of JUnit 4 please add support for JUnit 5 as well

Build

• 12/21 - Bump version to 0.2.0 (PR #61 #63) - @ansyral
• 12/21 - Add change log for 0.2.0 - @ansyral
• 12/21 - Signed RC Bits - @ansyral

Test

• 12/21 - Run test plan #49 - @bsaby @sallyur (found new bug #65 #66)
• 12/21 - Test multi-module project - @ansyral
• 12/21 - Test report on Mac - @akaroml
• 12/21 - Test test explorer for multiroot - @yaohaizh
• 12/21 - Test basic feature on Linux - @yaohaizh

Release

• 12/22 - Add 0.2.0 tag for vscode-java-test - @ansyral
• 12/22 - Release to marketplace - @ansyral

Notes

Before you check an item, please reply to this issue with the following details:

1. What are the steps and details of your check?
2. What are the configurations?
3. What are the issues found in the process?
4. What's your conclusion?

I have a vanilla Spring Boot app, and when running the default integration test supplied the test runner just hangs in the "Running tests..." state. I can see that the tests actually execute by looking at the test output window, but it seems it never returns the state. Normal unit tests without spring context works 100%.

Sample Class:

@RunWith(SpringRunner.class)
@SpringBootTest
public class MyApplicationTests {

    @Test
    public void contextLoads() {
    }  

}

Our tests make heavy use of https://github.com/TNG/junit-dataprovider. All of those are skipped. Furthermore, if I run all tests of a class (by clicking the Run Test button above the class declaration), even the plain JUnit tests are skipped as soon as the data-provided tests are encountered.

Are you planning on supporting the dataprovider package?

color is not right for black theme:

small:

Environment

• Operating System: win10 x64
• JDK version: 1.18.0_152 x64
• Visual Studio Code version: 1.18.1 x64
• Java test extension version: #22

Now we use different colors to reflect different result state. And we need to change a bit:

1. Running - default color (white)
2. All passing - green
3. 1 or more errors - red
4. Initial (no results) - default color (white)

I want to use Junit. But I don't know how to install it...

I have Java Test Runner installed. But not Junit

Somebody help!

Open spring-boot-junit-project, click Debug Test on some test case, it could pop up message box saying "Failed to attach to remote debugger VM. Reason: java.net.ConnectException: Connection refused (Connection refused)".

This issue didn't happen very frequently, but i have saw it several times. So still need a look.

Open Color checker test project, find ColorCheckerUnitTests.java file.

1. Add a breakpoint Line 79, and click Debug Test to debug test case testShouldReturnSameValues.
2. The program stops at Line 92, that belongs to another test case testShouldNotReturnTheSameValues, not my target test case.

After running test, click on class codelens or test statistics from status bar to open class report

As soon as I navigate away from a test file the Test Runner disappears. When I navigate back to a test file the Test Runner re-appears but the tree is collapsed.

I'm trying to make this extension work, but the first letter of the class name is always cut off. The problem is depicted in these Pictures:

The name of the Test is always missing the first letter of the class name, thats whats causing the error.
The class' name is "TestThis", but the name of the test that is being run is "estThis". This happens with every other letter too and i have no idea whats causing this.

JUnit itself works fine with this test, if i run it manually.

I have no idea what could cause this on my end and have not found any mention of this in other issues.

Environment

• Operating System: mac
• JDK version: 1.18.0_144
• Visual Studio Code version: 1.18.1
• Java test extension version: build25

Current result:

If do not choose org.junit, run class the method will failer.

It doesn't repro in windows.

Sample:
Method test result file:

Class test result file:

both of them have same file name, when i save files of them at the same time, Is it reasonable to always save the class test result file?

Run Color checker test project, if click Debug Test multiple times at the same location, it will launch duplicated test servers.

If ignore one testcase, the duration of all testcases will be NaN but I think it should be the sum of the rest testcase duration

After disable one case

Before disable one case

Build

• 11/30 - Instrument production AI key - @testforstephen
  (Jenkins RC build job)
• 11/30 - Bump version to 0.1.0 - @testforstephen
  (PR #16)
• 11/30 - Add change log for 0.1.0 #15 - @yaohaizh
• 11/30 - Signed RC Bits - @testforstephen
  (#2)
  (#3) that fixed blocking bug, please use this one for final verification.

Test

• 11/30 - Run test plan vscjavaci/java-test-ci/#1 - @bsaby @sallyur
• 11/30 - Java 9 support on Mac - @testforstephen
• 11/30 - Java 9 support on Linux/Ubuntu - @yaohaizh
• 11/30 - Validate production BI data - @ansyral @JialinXin

Release

• 11/30 - Add 0.1.0 tag for vscode-java-test - @testforstephen
• 11/30 - Release to marketplace - @testforstephen
  https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-test

Notes

Before you check an item, please reply to this issue with the following details:

1. What are the steps and details of your check?
2. What are the configurations?
3. What are the issues found in the process?
4. What's your conclusion?

We need an explorer to show all the cases inside the current workspace.

Users should be able to run and debug test cases by right-clicking the tree nodes.

Are the test messages (commands, results) conform to any existing protocol that could be reused in other tools? Is this an extension of the debug-server protocol with additional message to report test progress and results?

When user opens a legacy test project that is using junit 3.8.1, no any Run Test and Debug Test codelens are displayed. It's better to show some message to guide user that the extension doesn't support the legacy junit project.

In most cases, the test report will not be updated automatically unless you close the previous one.

1. Open a project
2. Run test a class: e.g. A class
3. Click the codelen of A class to open test report
4. Add @ignore on one method in A class
5. Run test A class again
6. Click the A class codelen
   

using the latest version it does not seem to show me the cancle/setting icon?

Error occured: ʮ���� 02, 2017 11:03:44 ���� org.springframework.context.support.ClassPathXmlApplicationContext prepareRefresh
��Ϣ: Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@532760d8: startup date [Sat Dec 02 11:03:44 CST 2017]; root of context hierarchy
Error occured: ʮ���� 02, 2017 11:03:44 ���� org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions
��Ϣ: Loading XML bean definitions from class path resource [beans.xml]
����û�
LinkedHashSet
����
����

Hello fellows,

in a project with several files an including some integration tests, I am trying to perform the following actions:

File csFile = new File("src/test/resources/Program.cs").getAbsoluteFile();

Let's say that my project is in C:\temp\myproject therefore i will expect to get something like:

C:\temp\myproject\src\test\resources\Program.cs

but instead i got:

Caused by: java.nio.file.NoSuchFileException: C:\Program Files\Microsoft VS Code\src\test\resources
	at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79)
	at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:90)
	at sun.nio.fs.WindowsLinkSupport.getRealPath(WindowsLinkSupport.java:259)
	at sun.nio.fs.WindowsPath.toRealPath(WindowsPath.java:836)
	at sun.nio.fs.WindowsPath.toRealPath(WindowsPath.java:44)
	at org.sonar.api.batch.fs.internal.DefaultInputModule.initBaseDir(DefaultInputModule.java:86)
	... 27 more

Is possible to setup the start folder for Junit?

I can run tests in a single module project, but as soon as I have multiple modules (e.g. opening up https://github.com/spring-cloud/spring-cloud-function/tree/master/spring-cloud-function-samples since that was what I was working on), I get this:

Error occured: Exception in thread "main" Error occured: java.lang.NoClassDefFoundError: org/junit/runner/JUnitCore
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
Error occured: 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at com.microsoft.java.test.runner.JUnitLauncher.main(JUnitLauncher.java:20)
Caused by: java.lang.ClassNotFoundException: org.junit.runner.JUnitCore
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	... 13 more

The code lenses for testing are not removed when the @Test annotation is removed from a test method.

It seems the spring boot context can't read configuration properly when running case, the test case src structure is followed maven default standard. The case can be executed on Eclipse IDE so it can't be case issue. Not sure if there is someway to config resource in test running to solve the issue. Thanks for your attention.

TestNG may be a bit of a niche, but it's a good and cozy niche to be in. Are there any plans to support it as well?

Environment

• Operating System: win10 x64
• JDK version: 1.18.0_152 x64
• Visual Studio Code version: 1.18.1 x64
• Java test extension version: #22

Current result:

We need to adopt the correct color scheme to highlight test results for users to easily read the test report.

I am not sure how it got to this stage, I was simply adding the logic for the tests.

Currently, we cannot see the numbers of passed or failed cases. This can be displayed inside the status bar.

Result:

Expect:

Now test reports are always shown in side view. This is disturbing for users with smaller screens (laptop).

Please add an option to show test report in side view (defauts to true). So when users set it to false, then the reports are shown in the current column.

package com.example.demo;

import java.util.Arrays;
import java.util.List;

import org.junit.Assert;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.junit.runners.Parameterized;
import org.junit.runners.Parameterized.Parameters;

@RunWith(Parameterized.class)
public class ParamTests {

    @Parameters
	public static List<Object[]> parameters() {
        return Arrays.asList(new Object[] {"foo"}, new Object[] {"bar"});
    }

   public ParamTests(String value) {}

   @Test
   public void test() {
   }
}

Click on "Run Test" on the class level and it runs them, but no status is available. And actually, if the test fails, it's just the same (status is a big "?").

Click on "Run Test" (on the @Test). Result:

@@<{"name":"testReporterAttached"}>
@@<{"name":"rootName", "attributes":{"name":"Default Suite"}}>
@@<{"name":"suiteTreeStarted", "attributes":{"name":"org.junit.runner.manipulation.Filter", "location":"java:test://org.junit.runner.manipulation.Filter"}}>
@@<{"name":"suiteTreeNode", "attributes":{"name":"initializationError", "location":"java:test://org.junit.runner.manipulation.Filter.initializationError"}}>
@@<{"name":"suiteTreeEnded", "attributes":{"name":"org.junit.runner.manipulation.Filter", "location":"java:test://org.junit.runner.manipulation.Filter"}}>
@@<{"name":"testSuiteStarted", "attributes":{"name":"org.junit.runner.manipulation.Filter", "location":"java:test://org.junit.runner.manipulation.Filter"}}>
@@<{"name":"testStarted", "attributes":{"name":"initializationError", "location":"java:test://org.junit.runner.manipulation.Filter.initializationError"}}>
@@<{"name":"testFailed", "attributes":{"name":"initializationError", "message":"No tests found matching Method test(com.example.demo.ParamTests) from org.junit.internal.requests.ClassRequest@5b80350b", "details":"java.lang.Exception: No tests found matching Method test(com.example.demo.ParamTests) from org.junit.internal.requests.ClassRequest@5b80350b\n\tat org.junit.internal.requests.FilterRequest.getRunner(FilterRequest.java:40)\n\tat com.microsoft.java.test.runner.TestRunnerUtil.getRequestForOneMethod(TestRunnerUtil.java:50)\n\tat com.microsoft.java.test.runner.TestRunnerUtil.createTestReferences(TestRunnerUtil.java:38)\n\tat com.microsoft.java.test.runner.CustomizedJUnitCoreRunner.run(CustomizedJUnitCoreRunner.java:26)\n\tat com.microsoft.java.test.runner.JUnitLauncher.main(JUnitLauncher.java:21)\n", "duration":"1"}}>
@@<{"name":"testFinished", "attributes":{"name":"initializationError", "duration":"2"}}>
@@<{"name":"testSuiteFinished", "attributes":{"name":"org.junit.runner.manipulation.Filter"}}>
Total tests run: 1, Failures: 1, Skips: 0

Currently, the test result stays when a user changes the actual test code. This could be misleading.

Please clear the test result whenever the test code is changed.

After install Java Test Runner extension, vscode pop up a message box saying Couldn't find Java home....
But vscode-java-debug and jdt.ls extensions can work successfully.

• Test Explorer #45
• Show test statistics in status bar #46
• Should not prompt save when closing test log #23
• Clear test result when test code changes #42
• Provide switch to optionally show output window #41
• Use the right color scheme to show test case status vividly #47
• Fix #34
• Make test report more user friendly

Test Plan - #49