Does Detox have its own HTML reporter?

No, and it doesn't need one — Detox runs through Jest, so any Jest reporter works. `jest-html-reporters` is the usual choice because it embeds attachments, which matters when Detox is producing screenshots.

What about the screenshots and video Detox records?

Detox writes them to the artifacts directory when you run with `--record-logs`, `--take-screenshots` or `--record-videos`. A reporter that references them produces a page you can publish with those files travelling alongside it as assets.

Can I publish a failing run?

Yes, and you should — a failing E2E run is the only kind anyone opens. Use `if: always()` on the publish step so a red build still produces the link.

Does this work on a CI machine with no display?

The report is just HTML, so yes. Where you run the simulator is a separate problem from where the result gets read, which is the whole point of publishing it.

Can a designer or PM look at it without an account?

Share the link at the access level you want — private, team, domain-gated, or named viewers. Commenting does not require a seat.

Share a Detox test report

An E2E failure in React Native is one of the hardest things to explain in text. The test says expect(element(by.id('checkout'))).toBeVisible() failed; what the reader needs is the screenshot of the screen where it wasn't, and maybe the simulator log around it.

Detox records all of that. It just leaves it in a folder on the runner.

Add a Jest HTML reporter

Detox drives Jest, so use Jest's reporter interface:

npm i -D jest-html-reporters

// e2e/jest.config.js
module.exports = {
  // …your existing Detox config
  reporters: [
    "default",
    ["jest-html-reporters", { publicPath: "e2e/report", filename: "index.html" }],
  ],
};

Then run with artifacts on:

detox test -c ios.sim.release \
  --take-screenshots failing --record-logs failing || true

--take-screenshots failing is the setting worth having — full recordings are large, failure screenshots are what get read.

Publish it

Drag the e2e/report/ folder into the app: index.html becomes the report body, and the embedded screenshots and attachments upload as assets with their references rewritten. 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 e2e/report/index.html \
        --arg title "Detox — $GITHUB_REF_NAME" '{title: $title, html: $html}')"

One id per suite, PATCHed on every run, if: always() so red builds publish.

What changes when it is a link

Anchored threads on the failing step, with the screenshot right there — "the button is off-screen on the SE, not missing." See commenting on HTML.
Revisions, so an intermittent failure has a history rather than a rumour.
No seat needed for the person who can tell you whether the screen is wrong or the test is.

Limits

Entry HTML: 5 MB. Assets: 25 MB per file, 250 MB and 500 files total. Video recordings are the ones that hit the per-file cap — publish screenshots and keep the video in CI storage.
60 requests/minute per token.

Try it

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

Publish an E2E report →