skills.rest
adityaarsharma
adityaarsharmaCOMMUNITY
Explore all skills by this author →
Website𝕏@adityaarsharmaGitHub

orbit-qa-flaky-detector

Detects and analyzes flaky tests in Playwright test suites.

2|1|Updated Apr 20, 2026
Search Tags:#root cause analysis#Playwright#flaky tests#test suite#test reliability
One-click install
npx skills add https://github.com/adityaarsharma/orbit --skill orbit-qa-flaky-detector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orbit-qa-flaky-detector
Source: https://github.com/adityaarsharma/orbit/tree/main/skills/orbit-qa-flaky-detector
Command: npx skills add https://github.com/adityaarsharma/orbit --skill orbit-qa-flaky-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

This Skill identifies and analyzes flaky tests in Playwright test suites, helping to maintain test suite reliability and performance.

Core Features & Use Cases

  • Flaky Test Detection: Identifies tests that pass-then-fail-then-pass, ensuring they are flagged for review.
  • Root Cause Analysis: Suggests potential root causes for flakiness, such as timing issues, network jitter, or parallelism problems.
  • Use Case: When you encounter intermittent test failures during continuous integration, use this Skill to diagnose and address the root cause.

Quick Start

Run the flaky test detector with 10 runs on your Playwright suite using the command: bash ~/Claude/orbit/scripts/detect-flaky.sh --runs 10.

Frequently Asked Questions about orbit-qa-flaky-detector

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

FAQPage Schema
How do I detect flaky tests in a Playwright test suite?▼

To detect flaky tests in a Playwright suite, run the detection script to execute your tests multiple times and identify those that inconsistently pass and fail. The tool flags these intermittent failures for review.

Why does my Playwright test suite have intermittent failures during continuous integration?▼

Intermittent Playwright test failures during continuous integration are often flaky tests. This Skill diagnoses them by suggesting root causes such as timing issues, network jitter, or parallelism problems.

What is the best way to find the root cause of flaky Playwright tests?▼

The best way to find the root cause of flaky Playwright tests is to analyze failure patterns across multiple runs. This tool identifies pass-then-fail-then-pass sequences and suggests causes like timing or network jitter.

Do I need Playwright installed to diagnose test suite reliability issues?▼

Yes, you need Playwright installed to diagnose test suite reliability issues with this tool. It requires Playwright and its associated scripts to execute the test runs and analyze the failures.

How many runs are needed to identify patterns of failure in flaky tests?▼

You can identify patterns of failure in flaky tests by running the detection script with a specified number of runs, such as 10. This repeated execution captures the inconsistencies needed for root cause analysis.

Related Skills

Explore More Software Engineering Skills→
sast-playgroundsast-playground

fix-flaky-test

Reproduce and resolve flaky tests by configuring environments, running tests, and analyzing results.

Official
Advanced
Camilo8902Camilo8902

flaky-test-detective

Diagnose flaky tests by analyzing execution logs and failure patterns.

Community
Advanced
CENKSSSCENKSSS

qe-test-execution

Orchestrate test suite execution with parallel sharding, retries, and real-time results.

Community
Advanced
kaiohenricunhakaiohenricunha

detect-flaky

Detect, diagnose, and fix flaky tests in Python, Go, and JavaScript/TypeScript codebases.

Community
Intermediate