Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#43,771 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
playwright, typescript
Área
testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

needs-triage
🚀 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.

Lenguaje dominante
TypeScript
Estrellas
98.5k
Forks
6.7k
Merge medio
17 h 5 min
PR fusionados (30 d)
326

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/playwright

Todos los issues de microsoft/playwright

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.