Does bun test produce an HTML report?

No. `bun test` writes to the terminal and can emit JUnit XML with `--reporter=junit --reporter-outfile=./junit.xml`, plus lcov coverage with `--coverage --coverage-reporter=lcov`. Convert either to HTML, then publish that.

How do I get HTML from bun test?

For coverage, `bun test --coverage --coverage-reporter=lcov` then `genhtml coverage/lcov.info -o coverage-html`. For results, convert the JUnit XML with a reporter like `junit2html`. Both give you a folder or file to publish.

Why publish instead of reading the CI log?

Because a failing run is read by people who cannot open your CI — a designer, a backend engineer on another team, a contractor without a seat. A URL reaches all of them; a log line reaches whoever has permissions.

Can I keep one link across runs?

Yes. Create the report once, store its id as a CI variable, and PATCH that id every run. Each publish appends a revision at the same URL, so bookmarks never go stale.

Can I attach failure screenshots?

Yes — as report assets, 25 MB per file and 250 MB per report. They live next to the results and the discussion instead of expiring with the CI artifact.

Share a Bun test report

Bun's test runner is fast enough that the run stops being the bottleneck. What is left as the bottleneck is everything after the run: the failure is in a CI log, the log needs a login, and the person who can explain the failure is the one without the login.

bun test has no HTML reporter — deliberately, it is a terminal tool — so the path to a link is a one-step conversion.

Two artifacts worth publishing

Results. Bun emits JUnit XML, the format every other tool in this space speaks:

bun test --reporter=junit --reporter-outfile=./junit.xml
npx junit2html junit.xml results.html

Coverage. Bun's coverage writes lcov, which genhtml turns into the familiar drill-down tree:

bun test --coverage --coverage-reporter=lcov --coverage-dir=coverage
genhtml coverage/lcov.info -o coverage-html

The coverage tree is the one that gains most from being a URL: its whole value is clicking from a directory to a file to the uncovered lines, and that is exactly what a screenshot of a percentage removes.

Publish it

Drag results.html — or the whole coverage-html/ folder — into Comma. For a folder, index.html becomes the report body and the per-file pages upload alongside it, with relative references rewritten to the uploaded copies, so the drill-down keeps working.

From CI:

bun test --reporter=junit --reporter-outfile=./junit.xml || TEST_FAILED=1
npx junit2html junit.xml results.html

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 "Tests — $GITHUB_REF_NAME" '{title: $t, html: $html}')"

exit "${TEST_FAILED:-0}"

Capturing the exit code and re-raising it after the publish is the pattern that matters: publish first, fail second, or the red run — the only one anybody needs — never gets a link. See publishing from CI and the API reference.

The failing test is a conversation

A failed assertion in a log gets a screenshot pasted into a channel, and the thread that follows has no connection to the run it is about. Published, the run has a URL, and the thread is anchored on the assertion — including the "this is flaky, third time this week" that is worth recording as a pattern rather than as a shrug. See commenting on HTML.

PATCHing one report id keeps a permanent URL and appends a revision per run, so "when did this start failing?" is answerable by opening the link rather than by hunting through expired artifacts. Compare expired CI artifacts.

Who can see it

Per report: private, your team, anyone signed in at your domain, or anyone with the link. See sharing & access control.

Limits

Entry HTML: 5 MB. Assets: 25 MB per file, 250 MB and 500 files total.
Scripts run, sandboxed — no same-origin access.
60 requests/minute per token.

Try it

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

Publish a test report →