-
Notifications
You must be signed in to change notification settings - Fork 78
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
Running --tests with multiple --tests parameters does not work as expected #2834
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. |
Created: forcedotcom/cli#2834 Adjusted the class to execute with comma separated versions.
you might want your shell script to echo out the command it's running. I'm sure this is an error in your bash script. Once you've done that, can you share the actual command that it's running? I just added a test to do your scenario (two |
Hi @mshanemc I have added that before. This is what is passing.
I have also tested with other formats such as
and all are giving errors, different from the initial one that is
To test locally what I do is to copy, from output the same sequence that the script outputs in the GHA. I will check out the issue you mentioned to see if it is not related to GHA as well. |
Those aren't issues, they're us running commands like yours (with 2 --tests) using GHA. Hopefully you can see some difference between those and your script |
* IS-788: Adjusting testing parameters. * IS-788 Adding visibility * IS-788 : Using the file instead. * IS-788: Adding debugging information to understand why the tests are failing * IS-788: Adding detailed coverage information * IS-788: Adding debug wrapper * IS-788:? Adding Test word to the component being tested. * IS-788: Force coverage display * IS-788: Removing test-coverage formatter It won't matter because the output fails before it displays the results. * IS-788: Adding one extra step to check on coverage * IS-788: Adjusting classes to run Instead of Json, using the comma separated value * IS-788: New Script format. Changing the test action to avoid warnings and only look on apex classes. * IS-788: Fixing a typo * IS-788: Adjustments * IS-788: Adjusting the typo again. * IS-788: Returning to older strategy which pass tests with comma separated. * IS-788: Fixing the flag not found error The issue is that it expects --tests "ClassTest" and not --tests ClassTest Adjusting * IS-788: Forgot this * IS-788: Using an XML Parser * IS-788: Forgot to remove the json file. * IS-788: Adding debugging Lines * IS-788: Troubleshooting differences of CLI * IS-788: Passing the tests with spaces instead of flags Documentation seems wrong, adjusting. * IS-788: Adjusting based on prior functioning script There is clearly a difference between plugins and sf cli. * IS-788: Trying to adjust the code to match current cli * IS-788: This seems to be a bug Created: forcedotcom/cli#2834 Adjusted the class to execute with comma separated versions. * IS-788: Separting the tests with spaces Returning to the very first version of the test. * IS-788: Returning to run all tests. Commented sections. * IS-788: Removing Typo * IS-788: Checking on node * IS-788: Forcing version * IS-788: Adjusting version * IS-788: Updating node * IS-788: Adding sudo to update node * IS-788: More sudo * IS-788: Last test run with all updated * IS-788: Returning to Full test run * Placing XML content in debug mode. * Removing debug comments. * IS-788: Remove apt-get update all Testing locally with act. * IS-788: Trying to run command locally * IS-788: No java * IS-788: Adding debuging information for local test. * IS-788: setting java to a pre-fixed version. * IS-788: Troubleshooting. * IS-788: Troubleshooting * IS-788: Troubleshooting * IS-788: Troubleshooting * IS-788: Troubleshooting * IS-788: Troubleshooting * IS-788: Troubleshooting * IS-788: Troubleshooting * IS-788: troubleshooting * IS-788: Troubleshooting. * IS-788: Using Snap * IS-788: Snap * IS-788: Adding a bash file to test changes. * IS-788: Some small adjustments to ensure that it won't throw errors. * IS-788: Adding validation for if file exists
Looks like from that PR you got the bash/quotes figured out. The CLI doesn't need the quotes, but bash var expansion and/or string concat might. I'll close this issue, but holler if I'm misunderstanding your PR. |
Hi @mshanemc yes, after awhile I managed to get it running. I'm still testing to see if it works with a lot of tests classes. The goal is to only run the test classes for the component being deployed. Thanks for the assistance. |
doctor
command to diagnose common issues.Context
Executed within Github Actions
Summary
The following command works on the development machine
Command:
but fails to work in a Github action using Ubuntu. The whole action is a big bash file.
Result
Steps To Reproduce
but it does not work under Github actions that are running under Ubuntu. The result in Ubuntu is:
Result
Executing the command with one single tag and tests separated by comma, generates a different issue:
Command:
Result
Expected result
Actual result
Result
System Information
Local Environment
Github Action Environment (ERROR environment)
Additional information
Note: Running using a file with a
json
containing which tests to execute, also does not work.Tests Done:
All of these tests done works with the MBP local environment.
Updates
The text was updated successfully, but these errors were encountered: