skills.rest
bitovi
bitoviOFFICIAL
Explore all skills by this author →
WebsiteGitHub

debug-e2e-test

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

46|3|Updated Mar 13, 2026
Search Tags:#automation#debugging#test failures#error analysis#playwright#e2e testing#ci
One-click install
npx skills add https://github.com/bitovi/vybit --skill debug-e2e-test-bitovi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-e2e-test
Source: https://github.com/bitovi/vybit/tree/main/.github/skills/debug-e2e-test
Command: npx skills add https://github.com/bitovi/vybit --skill debug-e2e-test-bitovi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It simplifies the troubleshooting process for failing Playwright end-to-end tests, enabling developers to quickly identify root causes and resolve issues.

Core Features & Use Cases

  • Analyze Test Failures: Provides a systematic approach to interpret test output, screenshots, and logs.
  • Artifact Inspection: Facilitates review of screenshots, error-context files, and test code to diagnose issues.
  • Use Case: When a Playwright test fails intermittently in CI, use this Skill to analyze the output, review screenshots, and determine whether it's a flaky test or a real bug.

Quick Start

Use the debug-e2e-test skill to investigate a specific failing test in your Playwright test suite.

Frequently Asked Questions about debug-e2e-test

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

FAQPage Schema
How do I debug Playwright E2E test failures in CI?▼

Debug Playwright E2E test failures by analyzing test output, screenshots, and error context. Review test artifacts and logs to identify root causes and determine whether failures stem from flaky tests or real application bugs.

What is the best way to analyze Playwright test screenshots and error context?▼

Analyze Playwright test screenshots and error context by inspecting generated test artifacts and logs. This artifact inspection process helps developers systematically diagnose issues and pinpoint the exact cause of intermittent test failures.

Can I run focused Playwright test reruns to debug complex issues?▼

Yes, you can run focused Playwright test reruns to debug complex issues. This workflow supports rerunning specific tests and enables live app interaction to observe behavior and facilitate resolution of failing end-to-end tests.

Why does my Playwright test fail intermittently in CI pipelines?▼

Intermittent Playwright test failures in CI can result from flaky tests or real bugs. Analyze test output, review captured screenshots, and inspect error-context files to distinguish between timing issues and actual application defects.

How do I troubleshoot flaky Playwright E2E tests?▼

Troubleshoot flaky Playwright E2E tests by engaging with test artifacts, logs, and code. Reviewing screenshots and error context systematically helps identify timing issues or environmental factors causing inconsistent test results.

Related Skills

Explore More Software Engineering Skills→
redhat-developerredhat-developer
170

e2e-parse-ci-failure

Extract failure context from CI job URLs or Jira tickets.

Official
Intermediate
moogieonmoogieon

qa

Automate QA testing and iteratively fix bugs in web application source code.

Community
Advanced
TalonT-OrgTalonT-Org
5

diagnose-ci

Fetch CI logs for a failing Git branch and classify failure types.

Official
Intermediate
BuilderIOBuilderIO
11

playwright-cli

Automate browser interactions and Playwright test workflows via command-driven tooling.

Official
Advanced