How do I share a Jest HTML report?

Generate one with `jest-html-reporter` (a single self-contained file), then POST it to https://commareports.com/api/v1/reports, or PATCH an existing report id so every run lands at the same URL. Reviewers open a page instead of downloading an artifact zip.

Does the Vitest HTML report work the same way?

Almost. Vitest's `--reporter=html` writes an `html/` directory whose index fetches its results as a separate file at view time, so publishing index.html alone renders an empty shell. Upload the sibling files as report assets alongside it — relative references are rewritten — or use a single-file reporter if you want the simpler path.

Which Jest reporter should I use?

`jest-html-reporter` emits one self-contained HTML file, which is the shape that publishes with a single curl. `jest-html-reporters` (plural) writes an HTML file plus an attachment directory, so upload that directory as assets.

How do I publish when the tests fail?

Make the publish step unconditional — `if: always()` in GitHub Actions, `after-script` in Bitbucket, `post { always { … } }` in Jenkins. A red build is exactly when someone wants the report, so a step that only runs on green defeats the purpose.

Can I keep one URL across every run?

Yes. Save the report id once, PATCH it on each run, and every run appends a revision at the same URL. Any two revisions can be diffed to see which tests changed state.

Share a Jest or Vitest HTML report

The default JS test report is a terminal scrollback, which is fine until someone who wasn't watching the terminal needs to see it. Then comes the HTML reporter, then the artifact upload, then the zip, then — reliably — a screenshot of the failure pasted into Slack.

The report is fine. It has no address.

One curl

npx jest --reporters=default --reporters=jest-html-reporter || true

curl -fsS -X PATCH \
  "https://commareports.com/api/v1/reports/$COMMA_REPORT_ID" \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html test-report.html \
        --arg title "Unit tests — $(git rev-parse --short HEAD)" \
        '{title: $title, html: $html}')"

jest-html-reporter writes one self-contained file, which is the shape that publishes in a single call. Use a scoped token (reports:write) from CI secrets, and PATCH a saved report id rather than POSTing — that keeps one URL with a revision per run instead of a new orphan link every build.

Vitest's HTML reporter has a directory

vitest --reporter=html writes html/index.html plus the result data beside it, and the page fetches that data at view time. Publish the index as the body and upload the siblings as assets:

for f in html/assets/* html/*.json; do
  curl -fsS -X POST \
    "https://commareports.com/api/v1/reports/$COMMA_REPORT_ID/assets" \
    -H "Authorization: Bearer $COMMA_API_TOKEN" -F "file=@$f"
done

Relative references are rewritten to the uploaded assets, so the page finds its data. This is the same pattern that Allure and Gatling need, and it's worth knowing once.

What the URL is for

Threads on failing tests. Highlight the assertion, pin a comment, and it survives the next dozen runs — see commenting on HTML.
Readers outside the repo. A designer checking a snapshot diff, a PM checking an acceptance suite. Sharing is per report.
Diffs between runs. Which tests flipped since the last green build, answered by a revision diff.
Slack on every push. A webhook on revision.created.

Limits

HTML body: 5 MB. Inline snapshots and base64 screenshots get there faster than you'd expect; move them to assets (25 MB/file, 250 MB/report).
Scripts run, sandboxed — allow-scripts, no allow-same-origin.
60 requests/minute per token.

Try it

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

Create your first report →

Coverage reports · Playwright · Cypress
JUnit XML → HTML — the language-agnostic route
GitHub Actions — if: always(), in context