skills.rest
nguyennd93
nguyennd93COMMUNITY
Explore all skills by this author →
GitHub

test-flakiness

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

Updated Jul 4, 2026
Search Tags:#flaky tests#test reliability#ci#test management#ci pipeline
One-click install
npx skills add https://github.com/nguyennd93/game_server_studio --skill test-flakiness-nguyennd93
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-flakiness
Source: https://github.com/nguyennd93/game_server_studio/tree/main/.claude/skills/test-flakiness
Command: npx skills add https://github.com/nguyennd93/game_server_studio --skill test-flakiness-nguyennd93

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detects and manages flaky tests in your Continuous Integration (CI) pipeline, helping maintain the reliability of your test suite.

Core Features & Use Cases

  • Flakiness Detection: Analyzes CI logs or test result history to identify tests that sometimes pass and sometimes fail.
  • Pass Rate Aggregation: Aggregates pass rates per test and identifies intermittent failures.
  • Remediation Recommendations: Recommends quarantining or fixing flaky tests and maintains a flaky test registry.
  • Use Case: Use this skill during the Polish phase or after multiple CI runs to ensure your tests are reliable.

Quick Start

Run the /test-flakiness command with the CI log path or use the 'scan' option to automatically detect flaky tests.

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 pipeline?▼

To detect flaky tests in a CI pipeline, you analyze CI log files or test result history to identify intermittent failures and aggregate pass rates per test. This process highlights tests that inconsistently pass or fail across runs.

What is a flaky test registry and how does it help with test reliability?▼

A flaky test registry tracks intermittent failures identified during log analysis, recommending actions like quarantining or fixing. Maintaining this registry helps isolate unpredictable tests to preserve overall test suite reliability.

Can I automatically scan test result history for intermittent failures?▼

Yes, you can automatically scan test result history for intermittent failures by pointing a script to your CI logs. The scan aggregates pass rates per test and identifies inconsistencies without requiring manual review.

When should I quarantine or fix a flaky test in my test suite?▼

You should quarantine or fix a flaky test after analyzing CI logs confirms intermittent failures. Quarantining isolates the unpredictable test to maintain pipeline stability, while fixing addresses the root cause of the flakiness.

Do I need access to CI logs to identify intermittent test failures?▼

Yes, access to CI logs or test result history is required to identify intermittent test failures. The analysis scripts parse this data to aggregate pass rates and detect inconsistencies across multiple pipeline runs.

Related Skills

Explore More Software Engineering Skills→
CarlosQ96CarlosQ96

test-flakiness

Analyze CI logs and test result histories to detect flaky tests.

Community
Advanced
jmaglyjmagly
175

flaky-detect

Analyze CI history and test execution patterns to identify flaky tests.

Community
Advanced
rakhnianskii9rakhnianskii9

test-flakiness

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

Community
Advanced
AZANIRAZANIR
2

qa-flaky-detector

Analyze CI history to classify flaky tests into four failure patterns.

Community
Intermediate