Reports and Cloud
Once results upload, they appear across the TestRelic cloud. This page maps captured data to where it surfaces.
API workspace for rest runs
Tests classified as rest API tests (because they made httpx or requests calls) open the API Session Workspace. There you inspect each captured request and response — headers (sensitive values masked) and bodies (truncated at the 32 KB default).
Assertions tab
Captured pytest assert statements appear with their source expression and evaluated values. For example, response.status_code == 201 is shown alongside its evaluated form 200 == 201, including failing assertions — so you can see precisely what broke. Per-test detail is available in the Run / Test detail view.
Captured streams
The plugin captures stdout, stderr, and caplog output per test, with redaction and a 32 KB-per-stream truncation default. Output beyond --testrelic-pytest-artifact-threshold-kb (default 32) is truncated inline.
Run-type buckets on the dashboard
When you pass --testrelic-pytest-run-type (smoke, regression, nightly, or ci), the run is grouped under that bucket on the Test Runs dashboard. This keeps CI stages distinct when you scan run history.
Metadata
Each run carries auto-detected CI metadata (GitHub Actions, GitLab CI, Jenkins, CircleCI) and git branch, commit, and author, with fallback to CI environment variables when .git is unavailable.
If a run could not upload (for example, the cloud was unreachable), it is held in the offline queue and replayed with testrelic-pytest drain. Check testrelic-pytest status for the pending count.