Run/Debug code lenses don't appear

[joshmanderson]

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?

[jdneo]

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

[joshmanderson]

@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]

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

[jdneo]

@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]

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]

@chrissantamaria Are you using Gradle as your building tools?

[chrissantamaria]

@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]

@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]

@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]

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

[jdneo]

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.