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

Testing Suite Fails to Actually Get tests #1675

Closed
NuAgeDan opened this issue Sep 20, 2019 · 5 comments
Closed

Testing Suite Fails to Actually Get tests #1675

NuAgeDan opened this issue Sep 20, 2019 · 5 comments

Comments

@NuAgeDan
Copy link

NuAgeDan commented Sep 20, 2019

Summary

See title. It reports "No Apex Tests Found" despite having Apex tests in the system (referenced with @istest). Yes the class has been compiled and saved to the org

Steps To Reproduce:

See summary

Expected result

Tests should show up

Actual result

Tests dont show up

Additional information

image

VS Code Version: 1.38.1

SFDX CLI Version: 7.25.3-16d54c01ee

OS and version: Win10. Not sure of version

@lcampos
Copy link
Contributor

lcampos commented Sep 20, 2019

Hi @NuAgeDan , can you confirm if the Apex language server is running without errors ? You can do this by opening VSCode's terminal then going to the Output section and selecting Apex Language Server in the dropdown on the right.

The Apex language server is the one that provides the data displayed in the Test sidebar so I wonder if there's an issue with it.

terminal_lang_server

@NuAgeDan
Copy link
Author

No errors, but a couple warnings:

  • INFO: Unsupported notification method: $/setTraceNotification
  • WARNING: Unmatched cancel notification for request id 12

@lcampos
Copy link
Contributor

lcampos commented Sep 27, 2019

Ok, if you open VSCode's Dev Tools (Help > Toggle Developer Tools and select the Console tab) do you see any errors ?

Is there a way you can share one of your apex tests ? We haven't been able to replicate this issue on our side.

@BrianEA
Copy link

BrianEA commented Oct 1, 2019

I ultimately had to clear out the sobjects/standardObjects and apex.db files under .sfdx/tools before this appeared to be resolved here. I had the same issue with tests being identified by the extension within the editor pages (and executable) but not listed in the Apex Tests panel.

@no-response
Copy link

no-response bot commented Oct 4, 2019

This issue has been automatically closed because there has been no response to our request for more information from the original author. Currently, there is not enough information provided for us to take action. Please reply and reopen this issue if you need additional assistance.

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

3 participants