Does Jasmine ship an HTML reporter?

It ships an HTML reporter for the browser runner, which renders in a live page rather than writing a file you can send. For a file, add `jasmine-reporters` and use its `JUnitXmlReporter`, then convert the XML.

How do I add the JUnit reporter?

Install `jasmine-reporters` and register `new reporters.JUnitXmlReporter({ savePath: 'reports' })` in a helper file that Jasmine loads before the specs.

What converts the XML to HTML?

`junit2html` (Python) or `junit-viewer` (npm) both take the file and emit a single page. Either is fine; pick whichever your image already has.

Can I publish a red run?

Yes — use `if: always()` on the publish step. The failing run is the one somebody needs to read, so publishing only on green inverts the value.

Does the published page stay interactive?

Report HTML renders with scripts enabled inside a sandboxed iframe, so a converted report's filtering and expandable failures keep working at the URL.

Share a Jasmine test report

Jasmine has been around long enough that most suites running it are the ones nobody wants to touch — which is exactly when a readable run matters, because the person deciding whether a change is safe is rarely the person who can run the suite.

The console reporter cannot help with that. jasmine-reporters can.

Write JUnit XML

npm i -D jasmine-reporters

// spec/helpers/reporter.js
const reporters = require("jasmine-reporters");

jasmine.getEnv().addReporter(
  new reporters.JUnitXmlReporter({
    savePath: "reports",
    consolidateAll: true,
  }),
);

consolidateAll: true gives you one file instead of one per spec file, which is what you want if the next step is a single page.

Convert and publish

npx jasmine || true
npx junit-viewer --results=reports/junitresults.xml --save=jasmine.html

Then drag jasmine.html into the app, or from CI:

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 jasmine.html \
        --arg title "Jasmine — $GITHUB_REF_NAME" '{title: $title, html: $html}')"

One id per suite. Every run becomes a revision of the same URL.

The browser runner

If you run specs in a real browser with the Jasmine HTML reporter, the page that renders the results is already HTML — screenshot-free publishing is a matter of saving it rather than converting anything. The same applies to a Karma report, which wraps the same idea in a runner.

Why publish it

Anchored threads on the spec in question, so "this one has been failing since the Node bump" is recorded where somebody will find it. See commenting on HTML.
Revisions across runs, which is the only honest way to argue about flakes.
Access per report — private, team, domain-gated, or named reviewers. See the sharing model.

Limits

Entry HTML: 5 MB. 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 a test report →