Share pytest-html results without mailing another self-contained file

pytest-html already renders environment info, filters, and captured output. ReportArk turns that file or folder into a controlled link your team can reopen during triage.

Generate a pytest-html package ready for upload

Stay inside your existing pytest workflow. ReportArk only needs the finished HTML output and any assets it references.

Install and invoke pytest-html
pip install pytest-html, then run pytest --html=report.html --self-contained-html (or omit self-contained if you prefer external assets).
Choose self-contained vs folder
Self-contained HTML is simplest: rename/copy to index.html and zip it. If you keep assets separate, zip report.html together with the assets directory using index.html at the archive root.
Upload from CI or laptop
After the job finishes, upload the zip via the ReportArk UI or automation skill. Reviewers never need a checkout of the repo to open results.

For Python test teams

pytest output is dense. Reviews need structure.

Failure dumps in CI logs scroll away. Hosting pytest-html keeps environment metadata, xfail/skip reasons, and captured stdout available while people assign follow-ups.

Filters and extras stay usable

Result filters, duration sorting, and embedded logs remain part of the hosted page—ReportArk does not flatten the report into a PDF.

Link across tools

Drop the share URL into Jira, Linear, or chat. Optional access passwords protect customer-specific suites without opening your whole CI.

Comments for flaky debates

When a test is contested, pin the discussion on the row in question instead of quoting stack traces into a separate channel.

FAQ

pytest-html sharing questions

Common packaging choices before upload.

Do I need --self-contained-html?

It is the easiest path because one file becomes index.html. Without it, include every referenced CSS/JS/image path in the zip with the same relative layout pytest wrote.

Can I upload raw JUnit XML?

No. ReportArk hosts HTML packages with an index.html entry. Convert or render with pytest-html (or another HTML reporter) first.

Will large captured logs work?

Yes within the platform upload size limit. Prefer concise captures in pytest when possible; oversized zips still fail the same safety checks as other reports.

Are pytest reports searchable on Google?

No. All report URLs and /r asset responses are noindex so UGC test output does not become public search spam on your domain.

Send the next pytest run as a review link

Keep authoring tests in pytest. When the HTML report is ready, host it once and point everyone at the same evidence.