Upload existing reports

testrelic upload imports test reports you already produce — Allure result directories, JUnit XML or CTRF JSON — into TestRelic Cloud, so historical and third-party runs land alongside runs from the SDK reporters. Performance runs from k6 and JMeter go through testrelic upload k6 and testrelic upload jmeter; see Performance testing.

Usage

# Allure results directory
testrelic upload --format allure ./allure-results \
  --repo my-org/checkout \
  --branch main \
  --environment staging \
  --run-type regression \
  --api-key tr_live_xxxxxxxx

# JUnit XML
testrelic upload --format junit ./reports/junit.xml \
  --repo my-org/checkout \
  --run-type ci

Or provide the key via the environment:

export TESTRELIC_API_KEY=tr_live_xxxxxxxx
testrelic upload --format allure ./allure-results --repo my-org/checkout

Approving an upload

Nothing leaves your machine until the upload is approved. In a terminal, the CLI asks you to confirm. In CI, in print mode (-p), or whenever its input or output is piped, it refuses and sends nothing unless you configure an approver or skip approval explicitly:

# skip approval in trusted CI
TESTRELIC_APPROVE_UPLOAD=1 testrelic upload ./reports/junit.xml --repo my-org/checkout
# or: --yes is a global flag, so it goes BEFORE `upload`
testrelic --yes upload ./reports/junit.xml --repo my-org/checkout

# or require an approver: the command gets the upload descriptor as JSON on stdin
# and must print {"approved":true}
testrelic upload ./reports/junit.xml --approver "cmd:./approve-upload.sh"

TESTRELIC_UPLOAD_APPROVER sets the approver from the environment. --dry-run never asks, because it sends nothing.

Uploading again

The run id comes from the report's contents, so uploading the same report again folds into the same run, and its screenshots, videos and traces aren't sent a second time: the platform doesn't de-duplicate artifacts, so they would appear twice. Pass --reupload-artifacts only when a first upload's artifact step partly failed: it resends all of them. From CLI 1.8.4, when the CLI retries an upload by itself after a server error, the run's artifacts are still sent.

Flags

Next steps

→ Authentication · Modes & engines