# How to Share Sauce Labs Test Results Outside Your Org

Canonical: https://commareports.com/share-sauce-labs-report
Published: 2026-09-14

> Sauce Labs jobs live behind an account and age out. Publish the run summary with failures, logs and screenshots so anyone can read it, now or next year.

# Share Sauce Labs test results

The suite ran across your platform matrix. Sauce Labs has the video, the
Selenium log, the screenshots — everything needed to understand the two
failures on Edge and on an older Android build.

All of it sits behind your Sauce account, and most of it will not be there in
six months.

## The two problems with sending a job link

**It needs an account.** Sauce supports public job links, and they are useful
for a single job. A release sign-off is not a single job; it is a matrix, and
handing someone twelve links without an overview guarantees nobody reads any
of them.

**It expires.** Artifact retention depends on plan. The link you attached to
the release ticket becomes a 404 long before the ticket stops being consulted —
the same failure mode as
[an expired CI artifact](/fix/ci-artifact-expired).

## Publish the run, not the jobs

Assemble one page after the suite finishes:

```html
<h1>Release 4.2 — cross-platform suite</h1>
<p>18 platforms · 16 passed · 2 failed · build 8823</p>

<table>
  <tr><th>Platform</th><th>Result</th><th>Failing test</th></tr>
  <tr><td>Edge 129 · Win 11</td><td class="fail">Fail</td>
      <td>checkout.spec — timeout waiting for #confirm</td></tr>
</table>

<h2>Edge 129 · Win 11</h2>
<img src="…failure.png" alt="Checkout stuck on spinner" />
<pre><!-- last 40 lines of the selenium log --></pre>
<p><a href="https://app.saucelabs.com/tests/…">Video in Sauce Labs</a></p>
```

Keep the video in Sauce and link it. Embedding video makes a page slow for the
90% of readers who only need the table.

## The page outlives the account

This is the argument that usually lands with a release manager. The summary is
a document you own: it does not expire on a retention schedule, it does not
require a seat, and it reads the same way in a post-incident review two years
from now as it did on release day.

The Sauce job is the evidence. The published page is the record.

## Failures get discussed where they are

A comment on the Edge row — "this is the known focus bug, ticket PLAT-2291" —
puts the triage next to the failure and keeps it there for whoever hits it
next. See [commenting on HTML](/comment-on-html).

## Worth knowing

- **Publish from CI**, right after the suite, updating one report id per
  release branch — see [publishing from CI](/ci).
- **Restrict the report.** Screenshots of unreleased builds should not be on
  an open link — see [security](/security).
- **Trim the logs.** Forty relevant lines beat four thousand; the full log
  stays in Sauce.
- **5 MB per report body.**

## Try it

Free — unlimited reports, commenters and revisions.

**[Publish from CI →](/ci)**

### Related

- [Share a BrowserStack test session](/share-browserstack-report) ·
  [Share a Maestro report](/share-maestro-report)
- [Share a WebdriverIO report](/share-webdriverio-report) ·
  [Share a Selenium-style JUnit report](/share-junit-report)
- [When a CI artifact expired](/fix/ci-artifact-expired) · [Publish from CI](/ci)