# How to Share a BrowserStack Test Session With a Client

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

> BrowserStack session links expire and need a seat. Publish the run summary with the failing cases, logs and screenshots as a page anyone can open.

# Share a BrowserStack test run

The regression suite ran across eleven browser and device combinations. Two
failed — Safari 16 on iOS and an older Samsung Internet — and BrowserStack has
the video, the console log and the screenshot for both.

The client's QA contact wants to see it. They do not have a seat on your
BrowserStack account, and you are not adding them to it.

## Two limits, not one

**Access.** Session details live behind your account. Public links exist but
are per-session: eleven combinations means eleven links and no overview, which
is exactly the shape nobody reads.

**Retention.** Session artifacts age out. The link you put in a Jira ticket is
a working reference for a few weeks and a dead end afterwards — the same
disappointment as
[an expired CI artifact](/fix/ci-artifact-expired).

## Publish the matrix

What a stakeholder actually needs is one page: what was tested, what failed,
and what the failure looked like.

```html
<h1>Cross-browser regression — release 2.14</h1>
<p>11 combinations · 9 passed · 2 failed</p>

<table>
  <tr><th>Browser / device</th><th>Result</th><th>Notes</th></tr>
  <tr><td>Chrome 141 · Win 11</td><td>Pass</td><td></td></tr>
  <tr><td>Safari 16 · iPhone 13</td><td class="fail">Fail</td>
      <td>Date picker does not open</td></tr>
</table>

<h2>Safari 16 · iPhone 13</h2>
<img src="…failure.png" alt="Date picker fails to open" />
<pre><!-- console output --></pre>
```

The table is what the client reads. The screenshots and logs underneath are
what their engineer reads. Both on one URL, which still works next quarter
because the summary is yours rather than BrowserStack's.

## Scope arguments end faster

The most common reply to a cross-browser report is not about the bug. It is
"do we even support Safari 16?"

On a published page that question arrives as a comment on the Safari 16 row and
is answered there, permanently, where the next person to ask will find it — see
[commenting on HTML](/comment-on-html). In email it gets re-litigated every
release.

## Publish it from the pipeline

```yaml
- run: npm run test:browserstack
- run: node scripts/publish-matrix.js   # builds the page, updates one report
```

Updating a single report id per release branch means one URL for "the current
cross-browser status", with the whole comment history attached. See
[publishing from CI](/ci).

## Worth knowing

- **Embed screenshots, link videos.** Video does not belong in a report body;
  a link plus a still keeps the page fast.
- **Restrict the report.** Screenshots of a pre-release app are not something
  to leave on an open link — see [security](/security).
- **5 MB per report body.**

## Try it

Free — unlimited reports, commenters and revisions.

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

### Related

- [Share a Sauce Labs report](/share-sauce-labs-report) ·
  [Share a Maestro report](/share-maestro-report)
- [Share a Playwright report](/share-playwright-report) ·
  [Share an Android test report](/share-android-test-report)
- [When a CI artifact expired](/fix/ci-artifact-expired) · [Publish from CI](/ci)