Run/Debug code lenses don't appear #470

joshmanderson · 2018-11-28T22:38:57Z

Starting about a week ago, code lenses for each test, as well as the lens for the test class as a whole, have stopped appearing. Also, no tests appear in the test explorer panel, though this may have been a pre-existing issue – I've never used the test explorer before so I can't say for sure.

Restarting or reloading vscode does not fix the problem, nor does restarting the computer, nor disabling and re-enabling the test runner code lens – or the root vscode code lens – setting (also tried disable+restart and re-enable+restart).

Project is using gradle and tests use junit. Gradle version was upgraded from 2.14.1 to 3.5.1 17 days ago, but the issue has only started occurring in the last week, so I'm not sure that the gradle upgrade is relevant to the problem.

Has anyone else experienced similar issues recently and does anyone have any ideas as to what might be causing the issue?

The text was updated successfully, but these errors were encountered:

jdneo · 2018-11-29T01:39:29Z

@joshmanderson Would you mind to share the project to us?

joshmanderson · 2018-11-29T03:02:14Z

@jdneo I can't do that, sorry – the project is private to my company.
I know that this certainly complicates the issue replication process, but I'm afraid it's just not possible for me to share it.

jdneo · 2018-11-29T03:10:28Z

@joshmanderson Ok I understand. I'll keep my eyes on this issue and update here if I find anything.

jdneo · 2018-11-29T09:41:42Z

@joshmanderson One more question.

Can you see the test explorer at the sidebar (though no test items in it), or there is no test explorer at all.

I‘m wondering if the extension gets activated successfully.

chrissantamaria · 2018-12-03T20:59:56Z

I'm having the same issue on two entirely separate machines; code lenses have stopped appearing and no tests are showing up in the Test Explorer either.

jdneo · 2018-12-04T02:04:13Z

@chrissantamaria Are you using Gradle as your building tools?

chrissantamaria · 2018-12-04T02:25:48Z

@jdneo Forgive me, I'm not all that experienced with Java packages, but I believe I am; I'm just using the standard Java Extension Pack. Projects were created with Eclipse beforehand.

jdneo · 2018-12-04T02:57:15Z

@chrissantamaria Don't worry.

Would you mind to share the content of .classpath file? Which is located at the base path of your project.

chrissantamaria · 2018-12-04T17:09:34Z

@jdneo

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="src" path="src"/>
	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-10">
		<attributes>
			<attribute name="module" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="con" path="org.eclipse.jdt.junit.JUNIT_CONTAINER/4">
		<attributes>
			<attribute name="module" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="output" path="bin"/>
</classpath>

joshmanderson · 2018-12-05T01:30:26Z

@jdneo Apologies for the late reply.
The test explorer appears in the sidebar, but there are no tests shown within it.

jdneo · 2018-12-05T01:46:31Z

I guess I got the root cause of this problem.

In our implementation, we will only search for the test items in the test folders. Here is the implementation to determine the location of the test folder.

But the implementation could not solve all the problems.

A valid .classpath file may look like this:

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="src" output="target/classes" path="src/main/java">
		<attributes>
			<attribute name="optional" value="true"/>
			<attribute name="maven.pomderived" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry excluding="**" kind="src" output="target/classes" path="src/main/resources">
		<attributes>
			<attribute name="maven.pomderived" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="src" output="target/test-classes" path="src/test/java">
		<attributes>
			<attribute name="optional" value="true"/>
			<attribute name="maven.pomderived" value="true"/>
			<attribute name="test" value="true"/>
		</attributes>
	</classpathentry>
	...
</classpath>

For some unknown reason, some projects may not have test attribute in its classpath entries. Just like @chrissantamaria provided. So I have to figure out a way to solve this scenario.

joshmanderson · 2018-12-05T22:49:28Z

@jdneo
I can confirm that changing my .classpath from this:

...
<classpathentry kind="src" path="src/test/java" />
...

to this:

<classpathentry kind="src" path="src/test/java" output="build/classes/test">
    <attributes>
        <attribute name="test" value="true" />
    </attributes>
</classpathentry>

fixes the issue. Tests are now appearing in the test explorer (and can be run from there), and code lenses are appearing again (and working).

jdneo · 2018-12-06T01:48:11Z

@joshmanderson Glad to know we have a workaround now. 😄

thoni56 · 2018-12-29T22:05:55Z

This workaround definitely worked for me too.

I had a project build in Eclipse that did not have "test" attributes in the classpathentry's. Adding this made the tests appear in the test explorer.

dampcake · 2019-07-15T21:50:06Z

@jdneo I have tried setting <testSourceDirectory/> in multiple different Maven projects and it doesn't seem to make a difference. It's always empty unless I manually edit the .classpath file.

Note that I am using the default src/test/java paths in all of these projects.

jdneo · 2019-07-16T01:23:58Z

@dampcake It would be helpful if you could share a sample project to repro the issue. This would be helpful for us to investigate what is going on?

dampcake · 2019-07-16T01:29:15Z

https://github.com/dampcake/bencode (small single module Maven sample).
https://github.com/dampcake/incubator-druid/tree/fix-eclipse (large multi-module Maven).

I have tried adding <testSourceDirectory/> in the parent pom.xml as well as in each individual child pom.xml for multi module projects. After adding I have even tried cleaning the Java workspace and restarting. Nothing I do outside of modifying the .classpath file directly seems to have any impact.

jdneo · 2019-07-16T02:51:24Z

@dampcake I tried the first one and it works on my side.

Here are some places that you may take a look:

Is the auto build turned on?
Try to trigger compilation task before running the test to see if it could help. It's F1 > Java: Force Java Compilation > Full
Is there any output in the output channel?

dampcake · 2019-07-16T05:27:10Z

Still not able to enable it:

Auto build is turned on.
Triggering a full build made no difference.
There is no output in the Java Test Runner output channel.

More info:
Java Test Runner version: 0.18.1
VSCode version: 1.36.1
OS: macOS 10.14.5
Java version: 1.8.0_201
Maven version: 3.6.0

Other things tried:

running git clean -fdX and opening to regenerate everything
cleaning the java server workspace

Screen shots:

jdneo · 2019-07-16T05:40:25Z

Hmmm, tried on Mac as well.

So far I've no idea what is going on. Would you mind to share the .classpath file that generated by the Java Language Server? You can find it at the root of your project.

dampcake · 2019-07-16T05:56:57Z

Here is the generated .classpath file:

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="src" output="target/classes" path="src/main/java">
		<attributes>
			<attribute name="optional" value="true"/>
			<attribute name="maven.pomderived" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="src" output="target/test-classes" path="src/test/java">
		<attributes>
			<attribute name="optional" value="true"/>
			<attribute name="maven.pomderived" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6">
		<attributes>
			<attribute name="maven.pomderived" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="con" path="org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER">
		<attributes>
			<attribute name="maven.pomderived" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="src" path="target/generated-sources/annotations">
		<attributes>
			<attribute name="optional" value="true"/>
			<attribute name="maven.pomderived" value="true"/>
			<attribute name="ignore_optional_problems" value="true"/>
			<attribute name="m2e-apt" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="src" output="target/test-classes" path="target/generated-test-sources/test-annotations">
		<attributes>
			<attribute name="optional" value="true"/>
			<attribute name="maven.pomderived" value="true"/>
			<attribute name="ignore_optional_problems" value="true"/>
			<attribute name="m2e-apt" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="output" path="target/classes"/>
</classpath>

jdneo · 2019-07-16T06:01:37Z

One thing I observed is that test scope is missing in the generated file. Here is mine:

<classpathentry kind="src" output="target/test-classes" path="src/test/java">
    <attributes>
        <attribute name="optional" value="true"/>
        <attribute name="maven.pomderived" value="true"/>
        <attribute name="test" value="true"/>
    </attributes>
    ...

dampcake · 2019-07-16T06:08:41Z

Yes and if added manually like in #470 (comment) it works, but it will not generate it with it in there. Was yours automatically generated like that?

jdneo · 2019-07-16T06:14:14Z

Yes it's automatically generated. Wired....

tthorntone · 2019-07-31T14:08:15Z

@jdneo Thanks for working this through with everyone! I'm experiencing another weird issue, related to this--

My .classpath does not by default generate the for my test sources, and my configuration is a bit complicated, so instead of a re-work I implemented this into my build.gradle:

def testSources = entries.findAll {element -> element.path == "src/test/java" || element.path == "src/test/resources" || element.path == "src/integrationTest/java" || element.path == "src/integrationTest/resources" }
  testSources.forEach { entry -> 
    entry.entryAttributes['test'] = 'true'
  }
}

This adds the test attribute, but at the bottom, see here:
Not Working ClassPath Gist

This does not work. However, if I let Eclipse do it , it generates the same xml, but with the test attribute at top, and it DOES work:
Working ClassPath Gist

jdneo · 2019-08-01T01:29:00Z

@dampcake is your problem get resolved?

If the test attribute is still not auto generated in your .classpath, I suggest to file an issue in the Language Server repo: https://github.com/eclipse/eclipse.jdt.ls

jdneo · 2019-08-01T01:37:23Z

Thank you @tthorntone for reporting this. I find a potential bug in the implementation. Let's discuss it in #759

dampcake · 2019-08-05T18:04:21Z

@jdneo it's still not working on my macbook. I just tried opening a couple projects today in Ubuntu and it's working fine there. I will try to dig in later this week and see if I can figure out what's going on.

rmgalante · 2019-10-09T20:44:06Z

I am unable to see the tests in the Test Explorer. However, I can run the Maven test command as follows and that works.

mvn test -f "c:\Users\xxx\Documents\xxx\Java\xxx\pom.xml"

All the tests run to completion. Here is my configuration.

VS Code Version: 1.39.0 (user setup)
VS Code Commit: 9df03c6d6ce97c6645c5846f6dfa2a6a7d276515

Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362

Java JDK 1.8.0.221
Language Support for Java v 0.50.0
Debugger for Java v 0.22.0
Java Test Runner v 0.20.0
Maven v 3.6.2

I tried the solution in Issue 470, and it did not solve the problem.

The Test Explorer is blank, and none of the CodeLens links appear in my unit tests.

jdneo · 2019-10-10T01:35:28Z

@rmgalante Any output in your output channel? Or any thing you can see in the problems panel?

rmgalante · 2019-10-10T08:33:07Z

I've cloned the open source repo, gozer, at https://github.com/walmartlabs/gozer. You should be able to duplicate this problem with that open source repo.

The Problem panel is empty. "No problems have been detected in the workspace so far."

The output panels shows the following exception when I launch the project. It does not look relevant to the problem as it is just the FileWatcher exception.

Looking for git in: C:\Program Files\Git\cmd\git.exe
Using git 2.21.0.windows.1 from C:\Program Files\Git\cmd\git.exe

git rev-parse --show-toplevel
git rev-parse --git-dir
git config --get commit.template
Open repository: c:\Users\xxx\Documents\xxx\Java\VSCode\gozer
git status -z -u
git check-ignore -v -z --stdin
git symbolic-ref --short HEAD
git rev-parse master
git rev-parse --symbolic-full-name master@{u}
git rev-list --left-right master...refs/remotes/origin/master
git for-each-ref --format %(refname) %(objectname) --sort -committerdate
git remote --verbose
Failed to watch ref 'c:\Users\xxx\Documents\xxx\Java\VSCode\gozer.git\refs\remotes\origin\master', is most likely packed.
Error: ENOENT: no such file or directory, watch 'c:\Users\xxx\Documents\xxx\Java\VSCode\gozer.git\refs\remotes\origin\master'
at FSWatcher.start (internal/fs/watchers.js:164:26)
at Object.watch (fs.js:1232:11)
at Object.t.watch (c:\Users\xxx\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\git\dist\main.js:1:594401)
at T.updateTransientWatchers (c:\Users\xxx\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\git\dist\main.js:1:98291)
at l.fire (c:\Users\xxx\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:539)
at k.updateModelState (c:\Users\xxx\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\git\dist\main.js:1:115979)

I can't use VS Code if I don't have a Task Runner. I hope this can be fixed.

adeick · 2020-02-15T20:41:07Z

I'm trying to figure out Debugging and Unit Testing for the first time. My class is using Eclipse, but I'd rather not download Eclipse if don't need to.
I have the Run/Debug Code Lense for the main method, but I do not have the Run Test/Debug Test Code Lense appearing on my Unit Test.

I'm not entirely sure where to edit the classpath. I have a bunch of .java files in a folder, but there isn't any .classpath file. I have my Visual Studio extensions stored in a completely different place on my computer. I have a .java file I want to use for testing, but it's not specified as a test file as far as I know.

I search for .classpath files in the File Explorer, and I found like 5 (they all look identical, I think they are for different versions of Java)
The one I have looks like:

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-12"/>
	<classpathentry kind="src" path="src"/>
	<classpathentry kind="output" path="bin"/>
</classpath>

And I changed the 2nd classpathentry line to what it said above, but it didn't work and I don't really know what I'm doing

jdneo · 2020-02-16T02:28:08Z

@adeick If your project for teaching purpose and is not complicated, you can use the standalone project in VS Code Java:

Just create a new empty folder.
In this folder, all the required libraries can be put into a folder named lib

See: https://code.visualstudio.com/docs/java/java-project/lib.mp4

ybelenko · 2020-06-10T21:30:06Z

I'm working in OpenAPITools/openapi-generator(latest master) repo. Tests panel is empty. No CodeLens actions in test files.
I tried to add .classpath file to root directory manually:

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="src" path="modules/openapi-generator/src/test/java/org/openapitools/codegen" output="build/classes/test">
        <attributes>
            <attribute name="test" value="true" />
        </attributes>
    </classpathentry>
</classpath>

Also tried to add <testSourceDirectory> to root pom.xml:

        <sourceDirectory>src/main/java</sourceDirectory>
        <outputDirectory>target/classes</outputDirectory>
        <testSourceDirectory>modules/openapi-generator/src/test/java/org/openapitools/codegen</testSourceDirectory>

Any suggestions?

Java Test Runner 0.23.0

MacOS Mojave 10.14.6

VSCode

Version: 1.46.0
Commit: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Date: 2020-06-10T08:59:06.977Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 18.7.0

Java SDK

$ java -version
java version "13.0.1" 2019-10-15
Java(TM) SE Runtime Environment (build 13.0.1+9)
Java HotSpot(TM) 64-Bit Server VM (build 13.0.1+9, mixed mode, sharing)

jdneo · 2020-06-11T12:30:48Z

@ybelenko I think it's because this project mixed with both Maven and Gradle, and the Java Language Server will import Gradle project by default.

I tried to disable the setting java.import.gradle.enabled and open the folder /modules/openapi-generator. The Code Lenses appear:

ybelenko · 2020-06-11T13:45:59Z

@jdneo Thanks a lot!

I've checked, it works under /modules/openapi-generator folder with disabled option.
Can I make it work somehow when VSCode opened with root directory?

See microsoft/vscode-java-test#470 (comment).

jdneo added the need more info label Nov 29, 2018

jdneo added bug and removed need more info labels Dec 5, 2018

jdneo mentioned this issue Dec 5, 2018

No test found to run when run test test project color-checker. #3

Closed

jdneo mentioned this issue Dec 7, 2018

Can't run test cases #508

Closed

This comment has been minimized.

Sign in to view

jdneo mentioned this issue Jan 6, 2019

Run tests fail #561

Closed

This comment has been minimized.

Sign in to view

jdneo mentioned this issue Jan 11, 2019

TestSuite are not discovered, can't launch test (since end of 2018) #576

Closed

SupinePandora43 mentioned this issue Jan 22, 2019

Junit5 test skipped #591

Closed

This comment has been minimized.

Sign in to view

mccreery mentioned this issue Feb 10, 2019

NPE occur when expanding the default package #611

Closed

This comment has been minimized.

Sign in to view

jdneo mentioned this issue Jul 15, 2019

docs: Add FAQ in the README.md #744

Merged

jdneo mentioned this issue Aug 1, 2019

Failed to resolve test scope #759

Closed

ericwill mentioned this issue Apr 14, 2020

Installing Java Test Runner Support for Java eclipse-che/che#14871

Closed

dr0i added a commit to hbz/lobid-resources that referenced this issue Dec 7, 2020

Fix missing junit test runner in codium

e9df5f0

See microsoft/vscode-java-test#470 (comment).

vswamire mentioned this issue Feb 9, 2021

Couldn't see test explorer and code lens for maven project #1139

Closed

dsyer mentioned this issue Sep 23, 2021

Code lenses for tests not showing #1310

Closed

3ter mentioned this issue Oct 22, 2022

couldn't start client language support for java(syntax server) redhat-developer/vscode-java#2561

Open

siddhsql mentioned this issue May 16, 2024

VS Code does not recognize junit tests #1692

Open

Run/Debug code lenses don't appear #470

Run/Debug code lenses don't appear #470

Comments

joshmanderson commented Nov 28, 2018 • edited Loading

jdneo commented Nov 29, 2018

joshmanderson commented Nov 29, 2018

jdneo commented Nov 29, 2018

jdneo commented Nov 29, 2018

chrissantamaria commented Dec 3, 2018

jdneo commented Dec 4, 2018

chrissantamaria commented Dec 4, 2018

jdneo commented Dec 4, 2018

chrissantamaria commented Dec 4, 2018

joshmanderson commented Dec 5, 2018

jdneo commented Dec 5, 2018 • edited Loading

joshmanderson commented Dec 5, 2018 • edited Loading

jdneo commented Dec 6, 2018

thoni56 commented Dec 29, 2018 • edited Loading

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

dampcake commented Jul 15, 2019

jdneo commented Jul 16, 2019

dampcake commented Jul 16, 2019

jdneo commented Jul 16, 2019 • edited Loading

dampcake commented Jul 16, 2019

jdneo commented Jul 16, 2019

dampcake commented Jul 16, 2019

jdneo commented Jul 16, 2019

dampcake commented Jul 16, 2019

jdneo commented Jul 16, 2019

tthorntone commented Jul 31, 2019 • edited Loading

jdneo commented Aug 1, 2019

jdneo commented Aug 1, 2019 • edited Loading

dampcake commented Aug 5, 2019

rmgalante commented Oct 9, 2019 • edited Loading

jdneo commented Oct 10, 2019

rmgalante commented Oct 10, 2019

adeick commented Feb 15, 2020 • edited Loading

jdneo commented Feb 16, 2020

ybelenko commented Jun 10, 2020

jdneo commented Jun 11, 2020

ybelenko commented Jun 11, 2020

joshmanderson commented Nov 28, 2018 •

edited

Loading

jdneo commented Dec 5, 2018 •

edited

Loading

joshmanderson commented Dec 5, 2018 •

edited

Loading

thoni56 commented Dec 29, 2018 •

edited

Loading

jdneo commented Jul 16, 2019 •

edited

Loading

tthorntone commented Jul 31, 2019 •

edited

Loading

jdneo commented Aug 1, 2019 •

edited

Loading

rmgalante commented Oct 9, 2019 •

edited

Loading

adeick commented Feb 15, 2020 •

edited

Loading