skills.rest
enbyaugust
enbyaugustCOMMUNITY
Explore all skills by this author →
GitHub

test-or-bug

Diagnose Playwright E2E test failures as code bugs or test issues.

30|3|Updated Jan 23, 2026
Search Tags:#debug#playwright#ci-cd#e2e-testing#diagnose#verdict#diagnostic-patterns
One-click install
npx skills add https://github.com/enbyaugust/zacs-claude-skills --skill test-or-bug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-or-bug
Source: https://github.com/enbyaugust/zacs-claude-skills/tree/main/skills/test-or-bug
Command: npx skills add https://github.com/enbyaugust/zacs-claude-skills --skill test-or-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams determine whether an end-to-end test failure is caused by a code bug or a faulty test, accelerating debugging and remediation.

Core Features & Use Cases

  • Structured diagnosis: Runs a 5-phase workflow to classify failures as CODE BUG, TEST ISSUE, BOTH, or UNCERTAIN.
  • Guided triage: Leverages diagnostic phases, error patterns, and verdict templates to produce actionable fixes.
  • Use Case: When a Playwright E2E test fails in CI with timeout or assertion errors, this Skill guides you to identify root cause and next steps.

Quick Start

Run the diagnostic workflow on a failing Playwright test and review the generated verdict, then follow suggested fixes.

Frequently Asked Questions about test-or-bug

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

FAQPage Schema
How do I diagnose if a Playwright E2E test failure is a code bug or a test issue?▼

To diagnose a Playwright E2E test failure, run a structured 5-phase workflow that analyzes errors, investigates code, and checks diagnostic patterns to classify the failure as a CODE BUG, TEST ISSUE, BOTH, or UNCERTAIN.

What is the best way to triage Playwright timeout and assertion errors in CI?▼

The best way to triage Playwright timeout and assertion errors is to apply a guided diagnostic workflow that reviews error patterns and code changes to generate an actionable verdict and suggested fixes.

Can I use this diagnostic workflow for local Playwright test failures as well as CI environments?▼

Yes, you can use this diagnostic workflow for local Playwright test failures as well as CI environments, because it applies to end-to-end tests across both when tests fail, time out, or produce unexpected results.

What are the phases of the end-to-end test failure diagnostic workflow?▼

The phases of the end-to-end test failure diagnostic workflow are running the test, analyzing errors, investigating code, checking diagnostic patterns, and producing a final verdict to classify the failure.

Why does my Playwright test fail with unexpected results and how do I identify the root cause?▼

Your Playwright test may fail with unexpected results due to either a code bug or a faulty test. You identify the root cause by referencing diagnostic guidance files and checking error patterns to produce a classified verdict.

Related Skills

Explore More Software Engineering Skills→
TeamDay-AITeamDay-AI
2

playwright-test

Automate end-to-end browser testing workflows with Playwright Test.

Official
Advanced
anton-abyzovanton-abyzov
156

e2e-playwright

Eliminate flaky Playwright end-to-end test failures across Chromium, Firefox, and WebKit.

Community
Advanced
TalonT-OrgTalonT-Org
5

diagnose-ci

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

Official
Intermediate
HabibTorjmenHabibTorjmen

debug-e2e

Debug failing e2e tests by delegating log analysis to subagents.

Community
Advanced