Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding new java package under test/src doesn't reveal tests in Test Explorer #758

Closed
stanlick opened this issue Jul 24, 2019 · 5 comments
Closed

Comments

@stanlick
Copy link

I started with a Spring Boot starter and the included tests worked fine. I added a new package and the tests never showed up under the test explorer. Strange, the folder name of the new source folder (package) was a different color as well. If I add new tests to the original folder, it all works great

@jdneo
Copy link
Member

jdneo commented Jul 25, 2019

Hi @stanlick,

I tried on my side but not able to repro the problem. Some questions might need your help to clarify.

  • Are you creating new package under test/src, or do you mean src/test/java.
  • Is it possible for you to share your sample project to let us help investigate the problem?

Thanks.

@stanlick
Copy link
Author

Project is here. It started off as a Spring project where I added a new folder (path segment) under test/java/com/example/demo named weird. I then added a MiscTests.java there that does not appear under Test Explorer.

Peace,
Scott

@jdneo
Copy link
Member

jdneo commented Jul 26, 2019

Thank you @stanlick

I can repro it now. Let me investigate the root cause. For now, a workaround would be reload the VS Code to make it appear in the explorer. Sorry for the inconvenience.

@jdneo jdneo added the bug label Jul 26, 2019
@jdneo jdneo added the upstream label Oct 12, 2019
@jdneo
Copy link
Member

jdneo commented Oct 12, 2019

Related with eclipse-jdtls/eclipse.jdt.ls#1137

@jdneo
Copy link
Member

jdneo commented Oct 15, 2019

Hi @stanlick,

The PR for fixing the upstream issue has been merged. I believe this problem will be addressed once the new version of Java Support extension get published.

So I'm closing this issue for now. If you find this problem still occurs after that, please feel free to let me know.

Thanks.

@jdneo jdneo closed this as completed Oct 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants