[Epic-Ideas-from-Alex] Observability in Test Explorer: traces, video and logs attached to each failed test

Cerrado
  • ¿Algo no está bien?
#3,448 0 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp, playwright
Área
observability, testing

Línea de trabajo

Start by reading the Playwright .NET test runner integrations for Visual Studio, VS Code, and Azure DevOps, then trace how test results and attachments are currently reported. The issue proposes per-test trace, video, screenshot, and log attachments, Trace Viewer links, OpenTelemetry spans, and structured logging. Done means failed test results expose the requested artifacts and links across the named test environments; the issue does not identify specific files or tests.

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

Descripción

🚀 Feature Request

Make debugging a failed Playwright test in Visual Studio / VS Code / Azure DevOps a one-click experience:

  • Attach artifacts to test results: trace.zip, video, screenshots and console / network logs as VSTest / MTP result attachments for each failed test.
  • "Open trace" from Test Explorer: a link or button that opens the Trace Viewer (local show-trace or trace.playwright.dev) for the selected failed test.
  • OpenTelemetry: emit an ActivitySource span per API call, correlated with the app under test (ASP.NET Core, HttpClient), so a failing step shows server-side spans next to it.
  • Azure DevOps / GitHub Actions: publish attachments in the format the test tab understands, plus a summary with direct trace links.
  • Structured logs via ILogger instead of Console.Error / DEBUG env vars.
Example

Test Explorer → failed CheckoutTests.Pay → Attachments: trace.zip, video.webm, console.log → Open in Trace Viewer.

In Azure Pipelines, the Tests tab shows the same attachments, and the run summary links each failure to its trace.

Motivation

Today the trace / video setup is hand-written per project, and the artifacts sit in folders disconnected from the test result that produced them.

Tying artifacts and telemetry to each test result is the biggest everyday time-saver for teams triaging CI failures. It also makes Playwright .NET competitive with integrated experiences in other ecosystems.

Lenguaje dominante
C#
Estrellas
3k
Forks
307
Merge medio
1 d 14 h
PR fusionados (30 d)
32

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-dotnet

Todos los issues de microsoft/playwright-dotnet

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.