UiPath CLI user guide

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

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

Arguments​

Options​

• --execution-id <uuid> (required) — execution to download.
• --project-key <key> — owning project. Either this or --test-set-key is required.
• --test-set-key <key> — test set key (for example, DEMO:42); the project key is derived from the prefix.
• --output-file <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 \
  --output-file ./junit.xml
uip tm result download \
  --execution-id a1b2c3d4-0000-0000-0000-000000000001 \
  --project-key DEMO \
  --output-file ./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
  }
}

Using the output in CI​

# 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.
• attachment — download screenshots, logs, and files produced by test case logs.

• Test Manager overview
• Scripting patterns