skills.rest
LeKay
LeKayCOMMUNITY
Explore all skills by this author →
GitHub

test-flakiness

Detect and categorize flaky tests in CI logs by pass rates.

Updated May 24, 2026
Search Tags:#quality assurance#CI/CD#software testing#test reliability#flaky test detection
One-click install
npx skills add https://github.com/LeKay/ai-game --skill test-flakiness-lekay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-flakiness
Source: https://github.com/LeKay/ai-game/tree/main/.claude/skills/test-flakiness
Command: npx skills add https://github.com/LeKay/ai-game --skill test-flakiness-lekay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill detects non-deterministic (flaky) tests by analyzing CI run logs or test result history, providing insights and recommendations to improve test suite reliability.

Core Features & Use Cases

  • Flaky Test Detection: Identifies intermittent failures in tests.
  • Analysis and Recommendations: Aggregates pass rates per test, recommends quarantine or fix actions, and maintains a flaky test registry.
  • Use Case: Integrate this Skill during the Polish phase or after multiple CI runs to ensure the stability of your test suite.

Quick Start

Analyze the flakiness of tests in the current CI run by running: /test-flakiness [ci-log-path].

Frequently Asked Questions about test-flakiness

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

FAQPage Schema
How do I detect flaky tests in my CI/CD pipeline?▼

Flaky test detection analyzes CI run logs to identify intermittent failures and aggregate pass rates per test. It categorizes non-deterministic tests to help maintain test suite reliability.

What is the best way to handle intermittent test failures in software testing?▼

Handling intermittent test failures involves analyzing test result history to categorize flakiness levels. The system recommends either quarantining or fixing the non-deterministic tests to restore suite stability.

When should I run flaky test detection during software development?▼

Flaky test detection is best used during the testing and Polish phases of software development. Running it after multiple CI runs ensures accurate analysis of test reliability and intermittent failures.

Can I automate flaky test detection using CI logs?▼

Yes, you can automate flaky test detection by passing your CI log path to the analysis script. It processes the logs to identify pass rates and maintain a flaky test registry for reliability tracking.

Does flaky test detection require specific quality assurance frameworks?▼

Flaky test detection does not require specific frameworks as it processes standard CI logs. It relies on test result history and pass rates to identify non-deterministic behavior across your runs.

Why does my test suite pass locally but fail in CI/CD runs?▼

Tests passing locally but failing in CI/CD indicate non-deterministic flaky tests. Analyzing CI run logs detects these intermittent failures by tracking pass rates and recommending quarantine or fix actions.

Related Skills

Explore More Software Engineering Skills→
rakhnianskii9rakhnianskii9

test-flakiness

Analyze CI run logs and test histories to detect flaky tests and maintain a registry.

Community
Advanced
MichaelSolatiMichaelSolati

test-flakiness

Parse CI logs and JUnit XML to detect flaky tests and classify root causes.

Community
Advanced
JaronTamJaronTam

bmad-testarch-ci

Generate and configure CI/CD pipelines with integrated testing and quality gates.

Community
Advanced
robit-manrobit-man

flaky-detect

Analyze CI history and code patterns to identify flaky tests.

Community
Advanced