Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature]: Support sharing self-contained HTML reports with embedded screenshots and attachments

Aperta
  • Qualcosa non va?
#43,771 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
playwright, typescript
Ambito
testing

Direzione di ricerca

Start by reading the HTML reporter documentation and implementation to find how the report references screenshots, attachments, and traces. Then assess whether embedding those assets or exporting a portable package fits the reporter architecture. Done means recipients can open a shared report and view its results and supported attachments without needing the original project.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

🚀 Feature Request

Currently, when using the HTML reporter, the generated report depends on additional files and directories for screenshots, traces, and other test artifacts. If I download and share only the index.html file with someone, the report may open, but screenshots and other attachments fail to load because their referenced files are not available.

The current workaround is to share the entire playwright-report directory as a ZIP file. The recipient must download and extract it, then run the show-report command from a Playwright project.

Example of the issue:
The screenshot below shows how an image appears broken when the HTML report is shared without its associated assets.

Image
Example

Introduce a configurable option in playwright.config.ts that allows users to generate a self-contained HTML report or a portable report package.

For example, an illustrative configuration could look like this:

reporter: [
  [
    "html",
    {
      outputFolder: "playwright-report",
      selfContained: true,
    },
  ],
],

The selfContained option is only a proposed API name; the implementation could use whichever configuration best fits Playwright's existing architecture.

Ideally, this feature would support one or both of the following approaches:

Single-file HTML report: Embed screenshots, images, and other suitable attachments directly into the HTML report so that users can share one file without broken references.

Portable report export: Provide a built-in way to package the HTML report and all required assets into a single archive or portable artifact that recipients can open without installing Playwright or creating a Playwright project.

The solution should preserve the existing report functionality as much as possible, including test results, failure details, screenshots, and trace access where technically feasible.

Motivation

This feature would make Playwright's HTML reporting workflow more convenient for teams that regularly share test execution results with developers, QA engineers, clients, and other stakeholders.

Key benefits include:

  • Prevent broken screenshots when sharing a standalone HTML report.
  • Eliminate the need to manually ZIP the report directory.
  • Allow recipients to view test results without installing Playwright or accessing the original repository.
  • Simplify the distribution of reports generated by CI/CD pipelines and distributed test runners.
  • Make test execution evidence easier to share, review, and retain independently of the original project.

I understand that embedding large screenshots, videos, and trace files could significantly increase the HTML file size. A portable archive option could be a practical alternative if generating a fully self-contained HTML report is not feasible.

Thank you for considering this feature. It would make Playwright reports significantly easier to share and review outside the original automation environment.

Lingua principale
TypeScript
Stelle
98.5k
Fork
6.7k
Merge medio
15h 42m
PR unite (30g)
313

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/playwright

Tutte le issue di microsoft/playwright

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.