CmdID

CmdID / az / az logicapp / az logicapp test / az logicapp test results

az logicapp test results show

Inspect a saved JSON test report without rerunning tests or following embedded paths. Azure CLI extensions reference

Accepts closed version 1.0 and 2.0 foundation preflight documents with notExecuted markers, preserving the recorded exit policy and source result. Validation is not a signature or provenance attestation. Exit 0 means inspection succeeded, never testsPassed; the source outcome and exit remain in inspection. Optional --workflow-file compares exact bytes and exits 5 on drift. Also accepts closed original execution reports from test run (logicapp-sdk-test schema 1.0). Native counts/outcomes are historical, retained under sourceOutcome/sourceExitCode, not new execution. Raw SDK/TRX files, unexpected fields and unknown producers are refused. Accepted JSON remains unauthenticated: schema validation is not proof of authorship.

1 example 2 options Its page in the Azure CLI extensions reference

Opens CmdID with your command. It is read in your browser and sent nowhere.

Examples

from the Azure CLI, each command read by CmdID

Inspect a saved preflight report (no tests executed) and check the current definition identity.

az logicapp test results show --result-file .\App\Reports\plan.json --workflow-file .\App\Orders\workflow.jsonIdentify
--result-fileSaved foundation preflight or sanitized test run JSON report.
--workflow-fileOptional explicit local workflow.json for byte identity comparison.

Options

2 in the Azure CLI extensions reference
--result-fileSaved foundation preflight or sanitized test run JSON report.
--workflow-fileOptional explicit local workflow.json for byte identity comparison.