Detect flaky tests by analyzing CI logs and test-result history.
npx skills add https://github.com/imclab/xrA1-swarm --skill test-flakiness-imclab
Please help me install this Agent Skill. Skill: test-flakiness Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/test-flakiness Command: npx skills add https://github.com/imclab/xrA1-swarm --skill test-flakiness-imclab
Detects flaky tests that intermittently fail or pass, preventing CI noise from masking real regressions and wasting developer time.
Use Case: After multiple CI runs, you suspect a subset of tests is unreliable and are getting frequent red builds; use this Skill to pinpoint which tests are flaky, estimate fail rates, recommend quarantine vs. fix, and document the rationale.
Run /test-flakiness scan to scan available CI logs and update tests/regression-suite.md with any detected flaky tests.
High-intent search queries and answers about installing and using this skill.
Detect flaky tests by aggregating per-test pass and fail outcomes across multiple CI runs from JUnit-like XML files, applying flakiness thresholds to identify tests that alternate results without code changes.
Test flakiness in regression suites is caused by timing issues, order dependency, randomness, resource leaks, external state, floating-point comparisons, and scene or prefab load races, which are classified by analyzing test result history.
Quarantine flaky tests by scanning CI logs to detect unreliable tests, then updating the quarantine section in tests/regression-suite.md and generating a dated flakiness report after explicit approval.
Yes, you can analyze plain-text engine logs from Godot, Unity, and Unreal to reconstruct per-test pass and fail history and detect flakiness across multiple regression suite runs.
Yes, test flakiness detection works with GdUnit4 and Unity NUnit by parsing JUnit-like XML test results to aggregate outcomes and apply flakiness thresholds across multiple CI runs.
You should quarantine a flaky test instead of fixing it when frequent red builds mask real regressions; the scan estimates fail rates and recommends quarantine versus fix actions to reduce CI noise.
MichaelSolatiParse CI logs and JUnit XML to detect flaky tests and classify root causes.
jmaglyAnalyze CI history and test execution patterns to identify flaky tests.
imgamerAnalyze CI logs and JUnit XML to detect intermittent test failures.
polseguDetect nondeterministic failures by parsing CI logs and aggregating per-test pass/fail histories.
