UiPath CLI - uip tm result

uipath-cli

latest

false

UiPath CLI user guide

uip tm result

Download execution artifacts in CI-friendly formats using `uip tm result`, including JUnit XML for test dashboards.

uip tm result downloads execution artifacts in a structured, CI-friendly format. It exposes one verb, which writes a JUnit XML file — the lingua franca consumed by most CI test dashboards (Azure DevOps, Jenkins, GitLab, CircleCI).

Synopsis

uip tm result download --execution-id <uuid> (--project-key <key> | --project-id <id> | --test-set-key <key>) [--result-path <path>]
uip tm result download --execution-id <uuid> (--project-key <key> | --project-id <id> | --test-set-key <key>) [--result-path <path>]

All verbs honor the global options and the standard exit codes.

uip tm result download

Download the results of a single test execution as a JUnit XML report. The command:

Fetches the execution's stats, test set name, and test set ID.
Pages through every test case log attached to the execution.
For each log, fetches the per-assertion artifacts in parallel (assertion lookup failures are logged and skipped, not fatal).
Fetches the test set's package list (best-effort — missing packages are silently omitted).
Serializes everything as JUnit XML and writes it to --result-path.

Arguments

None.

Options

--execution-id <uuid> (required) — execution to download.
--project-key <key> — owning project key.
--project-id <id> — owning project ID. Use instead of --project-key.

Pass --project-id, --project-key, or --test-set-key. When you pass more than one, --project-id is used first, then --project-key, then the project prefix of --test-set-key.
--test-set-key <key> — test set key (for example, DEMO:42); the project key is derived from the prefix.
--result-path <path> — output location. Can be a file path (./junit.xml) or a directory (the file is named after the test set). Defaults to the current working directory.

Example

uip tm result download \
  --execution-id a1b2c3d4-0000-0000-0000-000000000001 \
  --project-key DEMO \
  --result-path ./junit.xml
uip tm result download \
  --execution-id a1b2c3d4-0000-0000-0000-000000000001 \
  --project-key DEMO \
  --result-path ./junit.xml

Data shape

{
  "Code": "ResultDownload",
  "Data": {
    "ExecutionId": "a1b2c3d4-0000-0000-0000-000000000001",
    "Format": "junit",
    "OutputPath": "./junit.xml",
    "TotalTests": 10,
    "Passed": 8,
    "Failed": 2,
    "Cancelled": 0
  }
}
{
  "Code": "ResultDownload",
  "Data": {
    "ExecutionId": "a1b2c3d4-0000-0000-0000-000000000001",
    "Format": "junit",
    "OutputPath": "./junit.xml",
    "TotalTests": 10,
    "Passed": 8,
    "Failed": 2,
    "Cancelled": 0
  }
}

The actual JUnit XML is written to OutputPath. The JSON envelope reports success plus summary counts.

Using the output in CI

Publish the file written to --result-path using your CI test reporter. Typical patterns:

# Azure DevOps
- task: PublishTestResults@2
  inputs:
    testResultsFormat: JUnit
    testResultsFiles: junit.xml
# Azure DevOps
- task: PublishTestResults@2
  inputs:
    testResultsFormat: JUnit
    testResultsFiles: junit.xml

# GitHub Actions
- uses: dorny/test-reporter@v1
  with:
    name: Test Manager
    path: junit.xml
    reporter: java-junit
# GitHub Actions
- uses: dorny/test-reporter@v1
  with:
    name: Test Manager
    path: junit.xml
    reporter: java-junit

testsets run — produces the ExecutionId consumed here.
wait — block until the execution is terminal before downloading results.
report — a human-readable summary if you do not need JUnit XML.
report export — a report file (Excel, PDF, or JUnit) that Test Manager builds instead of the CLI.
attachment — download screenshots, logs, and files produced by test case logs.

uip tm result

Synopsis

uip tm result download

Arguments

Options

Example

Data shape

Using the output in CI

See also

Was this page helpful?

Synopsis​

uip tm result download​

Arguments​

Options​

Example​

Data shape​

Using the output in CI​

Related​

See also​

Was this page helpful?

Synopsis

uip tm result download

Arguments

Options

Example

Data shape

Using the output in CI

Related

See also