For QA teams

Publish test run reports, visual diffs, and reproduction packets as links that a developer can open from the ticket without downloading a build artifact.

The situation

Your test runs produce rich HTML reports that almost nobody opens, because opening them means finding the run, downloading a zip, and unpacking it. Meanwhile bug tickets get screenshots pasted in and the actual evidence stays buried.

What you are publishing

Test run reports
Suite results with failures, traces, and timing, rendered as a document that opens in one click from the ticket.
Visual regression diffs
Before, after, and difference views side by side in a single page a reviewer can scan quickly.
Reproduction packets
Steps, environment detail, console output, and evidence assembled into one artifact attached to the bug.

What matters most here

One click from the ticket

A URL pasted into the issue opens the report directly. No build system login, no download, no unzip.

Reports expire with the sprint

Set retention to match how long the run stays relevant so old reports clear themselves.

Evidence stays together

A project link keeps the report, the diffs, and the reproduction packet in one place instead of three attachments.

Published by the runner

The test job publishes and emits the URL, so the report exists before anyone thinks to ask for it.

How the workflow runs

  1. 01Configure the test reporter to emit a single self-contained HTML file.
  2. 02Publish it from the CI job, titled with the run and branch.
  3. 03Post the URL into the ticket or the run summary automatically.
  4. 04For a bug, publish the reproduction packet into a project alongside the failing run.
  5. 05Let sprint-scoped reports expire.

The questions this team asks first

Our reporter outputs a folder, not one file

Most reporters have a single-file or inline-assets mode; that is the setting you want. If yours does not, the report is closer to a small site and belongs on static hosting instead.

Screenshots make the report huge

Embedded images are usually the size problem. Compress them, or attach only failure screenshots rather than every step. Builder allows 10 MB per document and Pro allows 50 MB.

Can a developer comment on the report?

Not in BinHTML. There is no commenting or approval workflow. Discussion stays in the ticket; the artifact is the evidence it points at.

Related reading