How do I get an HTML report from Bruno?

`bru run --reporter-html results.html` from inside the collection folder. It writes a single self-contained file with every request, its assertions, status codes and timings.

Can I run only one environment or folder?

Yes — `bru run folder-name --env staging --reporter-html results.html`. The report reflects exactly the subset you ran, which is usually what you want to send someone.

Does Bruno's CLI need a login or a cloud account?

No. Bruno collections are plain files in your repository and `bru run` is a local CLI, which is most of why teams move to it. Publishing the report keeps that property — the collection stays in git, only the result gets a URL.

Can I publish the report when a request fails?

Yes, and that is the run worth publishing. `bru run` exits non-zero on assertion failures, so capture the code, publish, then re-raise it.

Can someone comment on a specific failing request?

Yes. Threads anchor to the rendered content, so "this 403 is expected, the token scope changed on Tuesday" stays on that request.

Share a Bruno API test report

Bruno's whole argument is that an API collection belongs in the repository, as files, under review, with no cloud account in the middle. That argument holds right up until a request fails in CI, at which point the result is back in a log that needs a login — the exact thing the collection was moved out of.

The CLI already writes the artifact that fixes it:

bru run --env staging --reporter-html results.html

One self-contained file: every request, the assertions that ran, status codes, response times, and the assertion that failed with what it got instead.

Publish it

Drag results.html into Comma, or publish from CI and keep one permanent URL per suite:

bru run --env staging --reporter-html results.html || FAILED=1

curl -fsS -X PATCH "https://commareports.com/api/v1/reports/$REPORT_ID" \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html results.html \
        --arg t "API — staging — $(date -u +%FT%TZ)" '{title: $t, html: $html}')"

exit "${FAILED:-0}"

Publish before failing the job, or the only runs that ever get a link are the green ones. See the API reference and publishing from CI.

Redact before you publish

An API test report contains request and response bodies, and those contain whatever your staging environment returns: bearer tokens in headers, customer records in payloads, internal hostnames.

Two things worth doing before the first CI publish:

Keep secrets in environment variables Bruno resolves at runtime rather than in the collection, so they are not in the repo or the report.
Set the report's access to private or team, not link-anyone. Access is per report — see sharing & access control.

The failure is a cross-team conversation

An API test fails for one of two reasons: the API changed, or the test was wrong about what the API does. Deciding which requires the person who owns the endpoint, who is on another team, probably in another repository, and does not have your CI.

A link they can open — with the request, the assertion, and the actual response in front of them — turns a two-day thread into a two-minute one. Anchored comments keep the verdict on the request: "intentional, we dropped legacy_id in v3". See commenting on HTML.

One URL per environment

The pattern that works: one saved report id per environment, PATCHed on every run. #api-staging and #api-prod-smoke become two stable links instead of a stream of artifact URLs, each publish appends a revision, and "when did this start failing?" is answered by scrubbing the history rather than by hunting expired artifacts — see expired CI artifacts.

Limits

Entry HTML: 5 MB. A collection with large response bodies can exceed it — Bruno's report includes them, so trim the assertions that dump whole payloads.
Assets: 25 MB per file, 250 MB and 500 files total.
60 requests/minute per token.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Publish an API test report →