The --junit and --coverage-formatters flags do not work with the --json flag for the sf project deploy start command.

[dpr-nh]

Summary

The --junit and --coverage-formatters flags do not work with the --json flag for the sf project deploy start command.

Steps To Reproduce:

1. Run the following command in a Salesforce project:

sf project deploy start --test-level RunSpecifiedTests --tests FileUtilitiesTest --source-dir force-app --results-dir ./tests/apex --junit --coverage-formatters text-summary --coverage-formatters text --coverage-formatters json-summary --coverage-formatters cobertura --dry-run --json

Expected result

The command should have created the ./tests/apex directory with the following architecture:

.
└── tests
    └── apex
        ├── coverage
        │   ├── cobertura.xml
        │   ├── coverage-summary.json
        │   ├── text-summary.txt
        │   └── text.txt
        └── junit
            └── junit.xml

5 directories, 5 files

Actual result

The directory ./tests/apex is not created. Running the same command without the --json flag does create the coverage and junit reports as intended.

System Information

• Which shell/terminal are you using?
  zsh

• sf version:

{
  "cliVersion": "@salesforce/cli/1.79.5",
  "architecture": "linux-x64",
  "nodeVersion": "node-v18.14.2",
  "osVersion": "Linux 6.2.15-300.fc38.x86_64",
  "shell": "zsh",
  "rootPath": "/home/dprnh/.nvm/versions/node/v18.14.2/lib/node_modules/@salesforce/cli",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 2.2.0 (core)",
    "@oclif/plugin-commands 2.2.15 (core)",
    "@oclif/plugin-help 5.2.9 (core)",
    "@oclif/plugin-not-found 2.3.23 (core)",
    "@oclif/plugin-plugins 3.0.1 (core)",
    "@oclif/plugin-search 0.0.17 (core)",
    "@oclif/plugin-update 3.1.15 (core)",
    "@oclif/plugin-version 1.3.4 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.37 (core)",
    "@oclif/plugin-which 2.2.20 (core)",
    "@salesforce/cli 1.79.5 (core)",
    "apex 2.2.19 (core)",
    "auth 2.7.15 (core)",
    "data 2.3.18 (core)",
    "deploy-retrieve 1.9.1 (core)",
    "info 2.6.13 (core)",
    "limits 2.3.15 (core)",
    "login 1.2.9 (core)",
    "org 2.9.0 (core)",
    "schema 2.3.10 (core)",
    "settings 1.4.8 (core)",
    "sobject 0.1.19 (core)",
    "source 2.10.9 (core)",
    "telemetry 2.2.0 (core)",
    "templates 55.4.15 (core)",
    "trust 2.4.18 (core)",
    "user 2.3.13 (core)"
  ]
}

Additional information

This bug was found while migrating CI/CD from the sfdx to sf command. The flags work as intended with the equivalent sfdx command.

[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.

[iowillhoit]

Confirmed using Dreamhouse.

Thanks for the issue @dpr-nh, we'll look into it.

[git2gus]

This issue has been linked to a new work item: W-13505809

[OlegBogdanovych]

Hello. What is approx ETA when this fix will be delivered? Thank you in advance

[cristiand391]

Hi @OlegBogdanovych , this is fixed in the latest release.