skills.rest
FlorinSenoner
FlorinSenonerCOMMUNITY
Explore all skills by this author →
GitHub

fix-tests

Resolve failing Playwright end-to-end tests with minimal fixes and full suite regression checks.

Updated Jan 24, 2026
Search Tags:#testing#debugging#e2e#regression#playwright#ci
One-click install
npx skills add https://github.com/FlorinSenoner/the-dahan-codex --skill fix-tests-florinsenoner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-tests
Source: https://github.com/FlorinSenoner/the-dahan-codex/tree/main/.claude/skills/fix-tests
Command: npx skills add https://github.com/FlorinSenoner/the-dahan-codex --skill fix-tests-florinsenoner

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the frustration and time loss associated with failing end-to-end tests, ensuring a stable and reliable testing environment.

Core Features & Use Cases

  • Systematic Failure Analysis: Identifies and diagnoses all failing tests.
  • Controlled Fixes: Applies minimal changes to resolve issues without introducing regressions.
  • Regression Prevention: Runs the full test suite after fixes to guarantee stability.
  • Use Case: When your CI pipeline fails due to broken Playwright tests, use this Skill to systematically debug and resolve the failures, restoring the green build.

Quick Start

Use the fix-tests skill to resolve all current Playwright E2E test failures.

Frequently Asked Questions about fix-tests

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

FAQPage Schema
How do I fix failing Playwright E2E tests in CI?▼

To fix failing Playwright E2E tests in CI, systematically analyze each failure, assess the blast radius of shared code changes, and apply minimal fixes. Run the full test suite after each resolution to prevent regressions and restore pipeline stability.

What's the best way to debug Playwright test failures without introducing regressions?▼

Debugging Playwright test failures without regressions requires applying minimal fixes and assessing the blast radius of shared code changes. After resolving individual tests, run the full end-to-end suite to validate stability and prevent new regressions.

Why do my E2E tests fail after shared code changes?▼

E2E tests fail after shared code changes due to the blast radius affecting multiple test paths. Systematically analyze each failure, apply minimal targeted fixes, then run the full Playwright suite to confirm no regressions were introduced.

Does this approach work for resolving flaky Playwright tests?▼

Yes, resolving flaky Playwright tests is supported by analyzing failures and applying precise wait strategies and selector usage. Running the full test suite after fixes ensures the end-to-end testing environment remains stable and reliable.

How do I prevent regressions when fixing broken end-to-end tests?▼

Prevent regressions when fixing broken end-to-end tests by applying minimal changes and running the full test suite after each individual test resolution. This controlled approach guarantees suite stability and prevents new failures.

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
plurigridplurigrid
60

qa-regression

Automate Playwright-based QA regression tests for login, dashboard, and user management flows.

Official
Advanced
DatTran26DatTran26

ck:test

Execute unit, integration, e2e, and UI tests with coverage reports.

Community
Advanced
willyu1007willyu1007

test-web-cypress

Automate end-to-end web UI testing with Cypress and generate CI artifacts.

Community
Intermediate