deploy validate NoTestRun not possible #3063
Labels
investigating
We're actively investigating this issue
validated
Version information for this issue has been validated
sf project deploy validate -x manifest/package.xml --test-level NoTestRun
Throws:
"Expected --test-level-NoTestRun to be one of : RunAllTestsInOrg, RunLocalTests, RunSpecifiedTests"
project deploy validate command should allow NoTestRun as you can do with deploy start.
sf version
{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.61.8",
"nodeVersion": "node-v20.17.0",
"osVersion": "Windows_NT 10.0.22631",
"rootPath": "C:\Users\0021559\AppData\Local\sf\client\2.61.8-ec7097b",
"shell": "powershell",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.2.5 (core)",
"@oclif/plugin-commands 4.0.16 (core)",
"@oclif/plugin-help 6.2.13 (core)",
"@oclif/plugin-not-found 3.2.22 (core)",
"@oclif/plugin-plugins 5.4.10 (core)",
"@oclif/plugin-search 1.2.10 (core)",
"@oclif/plugin-update 4.5.10 (core)",
"@oclif/plugin-version 2.2.14 (core)",
"@oclif/plugin-warn-if-update-available 3.1.18 (core)",
"@oclif/plugin-which 3.2.15 (core)",
"@salesforce/cli 2.61.8 (core)",
"apex 3.5.0 (core)",
"api 1.2.2 (core)",
"auth 3.6.65 (core)",
"data 3.6.8 (core)",
"deploy-retrieve 3.12.15 (core)",
"info 3.4.9 (core)",
"limits 3.3.32 (core)",
"marketplace 1.2.26 (core)",
"org 4.6.0 (core)",
"packaging 2.8.12 (user) published 3 days ago (Sat Oct 12 2024)",
"schema 3.3.34 (core)",
"settings 2.3.23 (core)",
"sobject 1.4.40 (core)",
"source 3.5.21 (core)",
"telemetry 3.6.15 (core)",
"templates 56.3.21 (core)",
"trust 3.7.32 (core)",
"user 3.5.32 (core)",
"@salesforce/sfdx-scanner 4.6.0 (user) published 21 days ago (Tue Sep 24 2024)",
"sfdmu 4.36.3 (user) published 26 days ago (Thu Sep 19 2024)",
"sfdx-essentials 2.12.0 (user) published 1036 days ago (Tue Dec 14 2021)",
"sfdx-git-delta 5.47.0 (user) published 7 days ago (Tue Oct 08 2024)",
"sfdx-hardis 5.2.2 (user) published 1 days ago (Mon Oct 14 2024)",
"texei-sfdx-plugin 2.8.0 (user) published 1 days ago (Mon Oct 14 2024)"
]
}
The text was updated successfully, but these errors were encountered: