-
Notifications
You must be signed in to change notification settings - Fork 26
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
sfdx force:apex:test:run fails when run from Github action #306
Comments
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
I'm not sure why this was moved from cli to the -vscode repo, it has nothing to do with the VS Code extension. |
I'm experiencing this issue across all of our sfdx projects in Github Actions. Most definitely not a VS Code extension issue. |
I am occasionally encountering this in a custom CI process. Following a successful I'm POSTing to |
I'm also getting "return code: 1" when running
|
I just ran into this issue, took me a day to figure out that if there are no Apex classes in the org that you are attempting to run the code in, the |
Summary
When we run
sfdx force:apex:test:run
from our ci/cd Github action, it fails with the error "ERROR running force:apex:test:run: Always provide a classes, suites, tests, or testLevel property."Steps To Reproduce:
Repository to reproduce: dreamhouse-lwc
We are using code based on the scratch-org-test job of ci-pr.yml in the dreamhouse repo.
Expected result
Test suite is run
Actual result
Error - "ERROR running force:apex:test:run: Always provide a classes, suites, tests, or testLevel property."
We have tried adding a
-l RunAllTestsInOrg
switch (also tried RunLocalTests, and using --testlevel) and still get the same error.System Information
Output after installing the sfdx-cli -
sfdx-cli/7.144.2 linux-x64 node-v16.14.2
This was previously working with v7.143.0
The text was updated successfully, but these errors were encountered: