🧪 QA & Testing · Test Automation

Eliminate flaky tests systematically

Quarantine, root-cause classes, and stabilization patterns restoring CI trustworthiness.

advanced~40 minQA EngineersSDETsTest Automation Engineers

Steps

1Auto-detect flakiness via retry-pass detection; report rate weekly
2Quarantine flaky tests immediately — a red CI must mean something
3Root-cause by class: timing/sleep → explicit waits; order-dependence → isolation
4Fix test-data collisions with unique-per-run factories
5Stabilize environment noise: ports, clocks, network mocks
6Burn down quarantine weekly; two-strikes rule for chronic offenders

Common Pitfalls

▲Auto-retry hiding flake instead of surfacing it
▲Deleting flaky tests silently losing coverage

Commands

Install with skills CLI

$ npx skills add aniruddhaadak80/skills --skill automation-flaky-test-elimination

Install globally

$ npx skills add aniruddhaadak80/skills --skill automation-flaky-test-elimination -g

Tags

#flaky-tests#ci#reliability#qa-testing#automation

Install this skill

$ npx skills add aniruddhaadak80/skills --skill automation-flaky-test-elimination -a opencode

SKILL.md

# Eliminate flaky tests systematically

> Quarantine, root-cause classes, and stabilization patterns restoring CI trustworthiness.

## When to Use This Skill

Quarantine, root-cause classes, and stabilization patterns restoring CI trustworthiness.

## Steps

1. Auto-detect flakiness via retry-pass detection; report rate weekly
2. Quarantine flaky tests immediately — a red CI must mean something
3. Root-cause by class: timing/sleep → explicit waits; order-dependence → isolation
4. Fix test-data collisions with unique-per-run factories
5. Stabilize environment noise: ports, clocks, network mocks
6. Burn down quarantine weekly; two-strikes rule for chronic offenders

## Common Pitfalls

- Auto-retry hiding flake instead of surfacing it
- Deleting flaky tests silently losing coverage

View source on GitHub ↗

Selector strategy and structure choices keeping end-to-end suites maintainable through UI churn.

🧪 QA & Testing·~35m

Open →

Write E2E tests that survive redesigns (Cypress)intermediate