skills.rest
redhat-developer
redhat-developerOFFICIAL
Explore all skills by this author →
Website𝕏@rhdevelopersGitHub

e2e-reproduce-failure

Reproduce and diagnose failing Playwright end-to-end tests with screenshots and traces.

170|222|Updated Jan 23, 2023
Search Tags:#testing#debugging#e2e#diagnostics#playwright#failure reproduction
One-click install
npx skills add https://github.com/redhat-developer/rhdh --skill e2e-reproduce-failure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-reproduce-failure
Source: https://github.com/redhat-developer/rhdh/tree/main/.cursor/skills/e2e-reproduce-failure
Command: npx skills add https://github.com/redhat-developer/rhdh --skill e2e-reproduce-failure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers reproduce and analyze failing end-to-end tests to determine their causes and consistency, aiding in debugging and quality assurance.

Core Features & Use Cases

  • Reproduction of Failures: Run specific e2e tests with Playwright and the healer agent to verify failures locally.
  • Failure Analysis: Collect detailed diagnostics, screenshots, and traces to understand flaky or persistent issues.
  • Use Case: When an automated test fails in CI, run this Skill locally to reproduce the failure, gather evidence, and decide whether to fix flakiness or investigate environmental differences.

Quick Start

Run the e2e-reproduce-failure skill to reproduce and troubleshoot a specific test failure in your local environment.

Frequently Asked Questions about e2e-reproduce-failure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reproduce a failing Playwright e2e test locally?▼

To reproduce a failing Playwright e2e test locally, run the specific test alongside the healer agent to verify the failure and gather diagnostic evidence in your local environment.

What is the best way to diagnose flaky e2e tests?▼

The best way to diagnose flaky e2e tests is to collect detailed diagnostics, screenshots, and traces during reproduction to determine whether the issue is persistent or environmental.

Can I collect screenshots and traces when an automated UI test fails?▼

Yes, you can collect screenshots and traces when an automated UI test fails by running the reproduction workflow, which captures detailed diagnostics for flakiness and failure analysis.

Does the healer agent work with Playwright for failure reproduction?▼

Yes, the healer agent works with Playwright by running specific e2e tests to verify failures locally, enabling detailed failure analysis and environmental troubleshooting for automated UI testing.

Why does my e2e test fail in CI but pass locally?▼

Your e2e test may fail in CI but pass locally due to environmental differences or flakiness, which you can investigate by reproducing the failure locally and gathering diagnostic evidence.

Related Skills

Explore More Software Engineering Skills→
SteveFeldmanSteveFeldman
5

e2e-setup

Automate Playwright end-to-end testing setup with page objects and CI integration.

Community
Advanced
LEEI1337LEEI1337
6

systematic-debugging

Identify root causes in technical issues before applying fixes.

Community
Basic
Euraika-LabsEuraika-Labs
14

test-flakiness

Detect flaky tests in CI logs from GitHub Actions, Unity, Godot, or Unreal.

Official
Advanced
pacphipacphi
14

Chrome DevTools

Debug web pages via Chrome DevTools MCP with performance, network, and DOM inspection.

Community
Advanced