-
Notifications
You must be signed in to change notification settings - Fork 77
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
project deploy validate with NoTestRun #2102
Comments
Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming or sprint planning session. We prioritize feature requests with more upvotes and comments. |
This issue has been linked to a new work item: W-13120962 |
The |
You can use this command "sfdx project deploy start -x manifest/package.xml -l NoTestRun --dry-run" with --dry-run parameter which will do the validation and the default test run level is no test run in this command |
@adityasfdev is correct - thanks! This is supported with the |
Are there any plans to update the validate command to respect NoTestRun. I understand there is a work around using the deploy start command, but it is not very intuitive. |
Even if a workaround is available, I think the command should be updated allowing using NoTestRun as explained by the documentation. |
I need to be able to do a Deploy check without running any test classes in Developer Sandbox to be able to test if the package.xml is valid and not missing any dependencies.
When running the following command by default all the local test are triggered
sf project deploy validate -x manifest/package.xml
sf project deploy validate -x manifest/package.xml -l NoTestRun
Expected --test-level-NoTestRun to be one of : RunAllTestsInOrg, RunLocalTests, RunSpecifiedTests
I would like to have NoTestRun available for the validate command.
As a workaround, I would run RunSpecifiedTests with a single random testClass
sf project deploy validate -x manifest/package.xml -l RunSpecifiedTests -t RandomClassTest
sf version
@salesforce/cli/1.75.6 win32-x64 node-V17.2.0
The text was updated successfully, but these errors were encountered: