skills.rest
ProjectEuropa
ProjectEuropaCOMMUNITY
Explore all skills by this author →
GitHub

e2e-debug

Diagnose failing Playwright E2E tests and CI regressions with repair steps.

4|Updated Jul 12, 2016
Search Tags:#automation#testing#debugging#e2e#playwright#ci
One-click install
npx skills add https://github.com/ProjectEuropa/Europa --skill e2e-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-debug
Source: https://github.com/ProjectEuropa/Europa/tree/main/.claude/skills/e2e-debug
Command: npx skills add https://github.com/ProjectEuropa/Europa --skill e2e-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Failing end-to-end tests and CI pipelines disrupt delivery; this Skill provides structured analysis and repair guidance to stabilize test suites.

Core Features & Use Cases

  • Analyze failing E2E tests across frontend (Playwright) and backend, identifying root causes.
  • Provide actionable remediation steps for flaky tests, timeouts, and CI regressions.
  • Generate error analysis reports and updated test objects to prevent recurrence.

Quick Start

Run the e2e-debug workflow against your test suite to trigger automated error analysis and repair suggestions.

Frequently Asked Questions about e2e-debug

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

FAQPage Schema
How do I fix flaky Playwright E2E tests and intermittent CI failures?▼

To fix flaky E2E tests, you need to analyze Playwright test results and CI logs to identify root causes across frontend and backend, then apply structured remediation steps for timeouts and intermittent regressions.

What is the best way to diagnose CI regressions in an E2E test suite?▼

Diagnosing CI regressions requires collecting local repro steps and CI logs to pinpoint the exact failure, allowing you to patch the failing end-to-end tests and verify the fixes prevent recurrence.

What do I need to provide to analyze failing end-to-end tests effectively?▼

Analyzing failing end-to-end tests requires Playwright test results, CI logs, and local repro steps to successfully diagnose, patch, and verify fixes for both frontend and backend regressions.

Can I use this approach to fix E2E test timeouts across both frontend and backend?▼

Yes, diagnosing E2E test timeouts is supported across frontend and backend, providing actionable repair guidance and updated test objects to stabilize the delivery pipeline against intermittent failures.

Why do my E2E tests keep failing intermittently during continuous integration?▼

Intermittent E2E test failures during CI happen due to flaky tests or regressions, which can be resolved by applying automated error analysis against your test suite to generate reproducible steps and repair guidance.

Related Skills

Explore More Software Engineering Skills→
bitovibitovi
46

debug-e2e-test

Diagnose Playwright E2E test failures by analyzing output, screenshots, and logs.

Official
Intermediate
DYAI2025DYAI2025

regression-test-generator

Generate Arrange-Act-Assert regression tests for Jest, Vitest, pytest, or Playwright.

Community
Intermediate
iCesofTiCesofT
1

e2e-testing

Automate Playwright end-to-end tests with a Page Object Model.

Community
Advanced
lane2077lane2077

ci

Analyze CI failure logs to identify root causes and remediation steps.

Community
Intermediate