test-reliability

Diagnose and repair flaky Playwright end-to-end tests at runtime.

2|Updated Apr 18, 2021
One-click install
npx skills add https://github.com/rabbicse/go-projects --skill test-reliability-rabbicse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-reliability
Source: https://github.com/rabbicse/go-projects/tree/main/projects/movie-ticket-booking/.claude/skills/test-reliability
Command: npx skills add https://github.com/rabbicse/go-projects --skill test-reliability-rabbicse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams diagnose and repair flaky tests that fail intermittently in CI or locally, reducing wasted reruns, false confidence, and noisy quarantine lists. It focuses on resilient test behavior when locators break, timing shifts, data expires, or environments behave differently.

Core Features & Use Cases

  • Flake classification: Distinguish timing, data dependency, environment, order dependency, time sensitivity, visual rendering, and external service issues.
  • Runtime healing: Apply multi-attribute selector repair, environment-aware diagnosis, and data regeneration instead of blind retries.
  • Observable repair workflow: Produce evidence, confidence scores, intent-fidelity checks, and quarantine routing for reviewable fixes.
  • Use cases: Stabilizing Playwright end-to-end tests, isolating recurrent CI flakes, managing quarantined tests, and tracking selector reliability across a suite.

Quick Start

Ask the skill to analyze a flaky test, classify the root cause, and propose an evidence-backed repair or quarantine plan.

Frequently Asked Questions about test-reliability

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

FAQPage Schema
How do I fix flaky Playwright tests in CI without using blind retries?

Fix flaky Playwright tests by classifying root causes like timing shifts or broken locators, then applying selector healing, data regeneration, and environment-aware diagnosis to produce evidence-backed repairs instead of unreliable blind retries.

What causes flaky end-to-end tests to fail intermittently?

Flaky end-to-end tests fail intermittently due to timing variations, expired test data, broken locators, test order dependencies, visual rendering shifts, or inconsistent CI environments requiring environment-aware diagnosis to isolate.

How do I heal broken Playwright selectors at runtime?

Heal broken Playwright selectors at runtime using multi-attribute selector repair, which updates locators dynamically and validates intent-fidelity to ensure the test targets the correct application element.

What is the best way to manage quarantined tests in a CI pipeline?

Manage quarantined tests in a CI pipeline by routing unstable tests to a quarantine list with confidence scores and evidence logging, ensuring fixes are reviewable while preventing false confidence from masked failures.

Why do my Playwright tests pass locally but fail in CI?

Playwright tests pass locally but fail in CI due to environment inconsistencies, timing variations, or expired test data, requiring environment-aware diagnosis and data regeneration to stabilize execution across differing environments.