Which WebdriverIO reporter produces HTML?

Community HTML reporters such as `wdio-html-nice-reporter` write a self-contained run report, and `@wdio/allure-reporter` plus the Allure CLI produces one too. Either way you end up with an HTML directory, which is what you publish.

How does this beat the CI artifact link?

The artifact is per-run, expires, and needs CI permissions. A published report is one URL per suite with a revision per run, readable by anyone you grant, and it keeps the comment threads across runs.

Do screenshots and video attachments work?

Yes — upload the report directory rather than only its index file so the referenced media uploads as assets and the paths are rewritten. An index published alone shows empty slots where the screenshots should be.

Can I keep separate reports per browser?

That is usually the right shape: one report id per capability, so Chrome and Safari each have their own URL and their own history instead of a merged report where a Safari-only flake is invisible.

Is the report public?

No — private by default, with access set per report. Staging screenshots tend to contain data that looks real enough to matter.

Share a WebdriverIO report

A WebdriverIO run produces a lot of context and almost none of it survives the trip to whoever needs it. The reporter builds a page with the steps, the screenshots, the logs. CI stores it for two weeks behind a login. The version that reaches the team is a red check mark.

Publish it

Generate the report the way your setup does — wdio-html-nice-reporter, or @wdio/allure-reporter followed by allure generate — then publish the directory:

npx wdio run wdio.conf.js || 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 reports/html-reports/master-report.html \
        --arg title "WDIO — $BROWSER — build $BUILD_NUMBER" \
        '{title: $title, html: $html}')"

Or drag the report folder into the app so the screenshots upload alongside and their references are rewritten to the uploaded copies.

|| true keeps the publish step running on a failed suite — the run you most want at a URL. One report id per capability: Chrome and Safari with separate URLs, so a browser-specific flake has its own visible history instead of averaging out inside a merged report.

What the URL changes

Threads on the failing step. With the screenshot right there. See commenting on HTML.
A history per suite. Revision per run at one URL, past the CI retention window. See revisions and diffs.
Readable by people without CI access — PM, designer, the person who filed the bug.
An agent can read the comments back through MCP when the thing fixing the test is Claude Code rather than a person.

Limits

Entry HTML: 5 MB. Assets: 25 MB per file, 250 MB and 500 files total. Video-on-failure is generous with both — record on failure only, or attach video as an asset rather than inline.
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 →

Share a WebdriverIO report

Publish it

What the URL changes

Limits

Try it

Related