---
title: "Report & Share Links"
id: "1923"
type: "page"
slug: "report"
published_at: "2026-09-30T22:18:24+00:00"
modified_at: "2026-10-01T00:11:02+00:00"
url: "https://xedant.com/agents/test/docs/report"
markdown_url: "https://xedant.com/agents/test/docs/report.md"
excerpt: "Showing a build right inside the product is not always convenient: a colleague needs a…"
---

# Report & Share Links

[https://xedant.com/agents/test/docs/report.md](https://xedant.com/agents/test/docs/report.md)

Showing a build right inside the product is not always convenient: a colleague needs a document, a customer a link, a pipeline a file. For that there are two ways — a printable report, and a share link that opens without signing in.

Both show exactly what the build proved. Neither the report nor the link turns a check into a release permission — those are different things, and the product does not mix them.

## The build report

The report is printed straight from the build page. The header carries the run’s verdict and the review state, the start and finish times, the branch and commit, the comparison engine, the environment, the window sizes, and the runner. Then come the sections for the problem steps: before, after and diff images, text comparisons, log lines, and failed checks.

Healthy steps do not get into the report. It stays a proof, not a listing: only what asks for attention is in it.

## The boundaries of this report

Every report — printed, exported, or from a green build — always prints a boundaries block. It cannot be removed by a setting, and that is deliberate:

- A visual check is not a business-logic check.
- A difference does not explain **why** the page rendered differently.
- A structure snapshot will not catch a visual defect, and a screenshot will not catch an accessibility problem: the layers see different things.
- The check gives evidence, not a release permission.

## Export for the pipeline

The report exports in forms build systems understand: a plain page and a data file. There is also a JUnit format — the check report build servers are used to, which they can show alongside the rest of the results. Every export is recorded in the audit log: you can see who took the report and when.

The exported page embeds thumbnails of only the first problem captures (up to fifty) — the rest stay in the product. That way the file never turns into a fifty-megabyte monster, and the recipient still sees the main thing.

## Share links

A share link gives an anonymous **read-only** view: no verdicts, no comments, and no credentials leak to the outside. The page carries a diagonal watermark with the product name and today’s date — it is always visible that this is published evidence, not a working screen.

You can publish a whole build or a single capture. The expiry is set from 1 to 90 days, two weeks by default. Republishing within a day returns the same link, so addresses do not jump around in a thread. A link can be revoked at any moment, and an expired one honestly answers that it is no longer available — instead of an empty page or a leaked image.

Next: how the pipeline understands on its own whether it may move on — in [CI & Notifications](/agents/test/docs/ci)
.

[← Back to the documentation index](/agents/test/docs)