Share Allure reports as a live HTML site, not a zip on chat

Allure’s strength is navigation across behaviors, packages, graphs, and attachments. ReportArk hosts the generated allure-report site so reviewers get that full SPA experience from one URL.

Preparing an Allure HTML report for secure sharing

Build the Allure HTML site before you upload

Allure separates raw results from the rendered website. Upload the rendered site—never only the allure-results directory.

Collect results from your runner
Configure pytest-allure, Allure JUnit, Cucumber, or your framework adapter to write allure-results/ during the test run.
Generate the report site
Run allure generate allure-results -o allure-report --clean (or the CI equivalent). Confirm allure-report/index.html opens locally with categories, graphs, and attachments.
Zip allure-report and upload
Archive the entire allure-report directory so index.html, app.js, data/, and widgets/ keep their relative paths. Upload that zip to ReportArk and share the link.

When Allure is your source of truth

History and attachments need a real web origin

Opening Allure via file:// or a short-lived CI artifact URL breaks deep links and confuses non-engineers. A hosted copy keeps executive-friendly overview tabs and engineer-grade attachments on the same durable link.

SPA routes keep working

ReportArk serves the static Allure bundle through the report asset pipeline, preserving client-side navigation across suites and behaviors.

Safer than a public bucket

View access is gated by the share model (link and optional password). Comments require approved accounts—viewers are not automatically editors.

Same URL across retries

When CI regenerates Allure for the same change set, owners can publish a new content version without rotating the share link reviewers already bookmarked.

FAQ

Allure sharing questions

Avoid the common “I uploaded results, not the report” mistake.

Why can’t I upload allure-results only?

allure-results is raw JSON for the generator. Browsers need the generated allure-report website with index.html and static assets.

Do I need allure open / a local server?

Not for reviewers. After ReportArk hosts the generated site, the share link replaces local allure open for anyone you invite.

Can attachments and screenshots load?

Yes if they were part of allure-report when you zipped it. Missing attachment files usually mean the generate step ran without those results present.

Will search engines list our Allure history?

No. Report shells and /r assets send noindex. Keep quality history on shared links, not in public search indexes.

Publish the next Allure site as a review link

Generate allure-report as you already do, upload the folder, and let product, QA, and engineering inspect the same graphs and failures.