sf deploy metadata validate -l NoTestRun

[amanjareck]

Note
Before you submit your issue, make sure that:

• You're using the latest version of Salesforce CLI.
• You've searched both open and closed issues for related posts.
• You've used the doctor command to diagnose common issues.
• You understand that GitHub Issues don't adhere to any agreement or SLA.
  • If you require immediate assistance, use official channels such as Salesforce Customer Support.

Summary

Steps To Reproduce

IMPORTANT
Provide a repository that's configured to reproduce the issue. If you are unable to provide a repo, please explain why not. The more info we have from the start, the faster we can resolve your issue.
We may close your issue if you don't include proper instructions.

• Generate a project with sf project generate or fork dreamhouse-lwc.
• Provide detailed step-by-step instructions on how to reproduce the issue.

Expected result

Actual result

System Information

PASTE_VERSION_OUTPUT_HERE

Additional information

[github-actions]

Hello @amanjareck 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue.
  • A repository that clearly demonstrates the bug is ideal.
• Make sure you've installed the latest version of Salesforce CLI. (docs)
  • Better yet, try the rc or nightly versions. (docs)
• Try running the doctor command to diagnose common issues.
• Search GitHub for existing related issues.

Thank you!

[github-actions]

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.

[mcarvin8]

@amanjareck I submitted a similar issue via #2470

I was advised that by design, validate is a pre-cursor to quick-deploy and thus, enforces test coverage to run.

To "validate" without running any tests, use the --dry-run option on the sf project deploy start command and omit the test level to run a validation without tests. Salesforce will scan the package and set tests to Not Required when the package.xml doesn't contain Apex .

Something like this:
sf project deploy start --dry-run -x manifest/package.xml --verbose

[mshanemc]

I came here to say exactly what @mcarvin8 said.

[amanjareck]

Thanks a lot, and thanks for catching regardless of lack of explanation and a more verbose log. This is good, the command I am looking at is not well documented so have to go old school and use help in command prompt. Been fixing our pipelines and missed this one.

Thanks once again guys :)