absolute-deflake
Flaky test fixes: detect nondeterministic tests empirically (repeat/shuffle/parallel runs), diagnose the root cause, fix it — never retry/skip/sleep — and verify across many randomized runs. Triggers on "absolute deflake", "fix flaky tests", "CI is flaky", "this test fails random
#workflow #testing
Install
npx skills add https://github.com/dhruvjainin/absolute/tree/main/skills/absolute-deflake
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install dhruvjainin-absolute@llmmart
git clone https://github.com/dhruvjainin/absolute.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole dhruvjainin/absolute collection as a plugin from our marketplace. Git is the plain clone.
README
absolute-deflake
Flaky test fixes. Detects nondeterministic tests empirically (repeat/shuffle/parallel runs), diagnoses the root cause (shared state, clock, network, concurrency), fixes it — never retries, skips, or sleeps.
Quick Facts
| Field | Value |
|---|---|
| Category | workflow |
| Version | 0.5.0 |
| Platforms | claude-code, gemini-cli, openai-codex, mcp |
| License | MIT |
How to Install
npx skills add maddhruv/absolute-deflake
Usage
/absolute-deflake "Fix the flaky tests in our CI"
/absolute-deflake "This test fails randomly"
Maintainers
Skill manifest
Start your first response with the 🧪 emoji.
Absolute Deflake
Find tests that pass and fail nondeterministically, diagnose the root cause of each, and fix it — not by retrying or skipping, but by removing the source of nondeterminism. Output is evidence (failure rate per test) → cause → fix, verified by repeated runs.
Runs the shared engine in references/health-engine.md — read it for the
DETECT → SCAN → TRIAGE → FIX → VERIFY → REPORT loop and the safety contract. This file
covers only what's specific to flaky tests.
When to use
- "Our CI is flaky", "this test fails randomly", "fix the intermittent failures".
- A test passes locally but fails in CI (or vice versa), or fails ~1 in N runs.
- Burning down a backlog of
retry/skip-marked tests that mask real flakiness.
Not for tests that fail deterministically — that's a real bug or a real regression
(/absolute work for a fix, or just fix it). deflake targets nondeterministic failures.
What it scans
Establish flakiness empirically — a test isn't flaky because someone said so. Use
preferences.health.deflakeRuns from config as the default N for repeat-runs (else 20):
| Ecosystem | Repeat-run / detect |
|---|---|
| Jest/Vitest | run suite N× (--run loop), randomize order (--shuffle / testSequencer) |
| pytest | pytest-randomly + pytest --count=N (pytest-repeat); -p no:randomly to A/B |
| Go | go test -count=N -shuffle=on ./..., -race |
Also mine signals: existing retry/flaky/skip annotations, CI history if reachable, and
run the suite both in isolation and in full/parallel — order- and concurrency-
dependent failures only show one way. Record a failure rate per suspect test.
Common root causes (diagnose, don't guess)
| Cause | Tell | Fix |
|---|---|---|
| Test-order / shared state | passes alone, fails in suite (or vice versa) | isolate state; reset/teardown between tests |
| Time / clock | fails near midnight, DST, or under load | fake timers / inject clock; no real sleep |
| Async race / missing await | fails under parallelism or slow CI | await the actual condition; no fixed timeouts |
| Randomness | fails ~X% with no pattern | seed the RNG; fix the seed in tests |
| Network / external I/O | fails offline or on slow links | mock/stub the boundary |
| Unordered collections | fails on map/set iteration order | sort before asserting |
| Resource leak / port reuse | fails on repeat or parallel runs | unique resources; clean up |
Risk ranking (TRIAGE)
| Wave | Class | Default |
|---|---|---|
| 1 | clear, isolated cause (seed, await, fake clock, sort) | fix now |
| 2 | shared-state / ordering — needs fixture refactor | fix this pass, per test |
| 3 | flakiness pointing at a real product race, not just the test | gated — surface; may be a genuine bug to fix in code |
A flaky test sometimes means the code has a race, not the test. Don't "stabilize" the test into hiding a real concurrency bug — flag wave-3 cases for a real fix.
Fix & verify
- Fix the cause. Then prove it: re-run the test many times (and shuffled / parallel /
with
-race) — green once is not deflaked; green across N randomized runs is. - Remove the
retry/skip/flakyannotation that was masking it once the cause is fixed. - Never "fix" by adding retries, raising timeouts blindly,
sleep, or skipping the test — that hides flakiness, doesn't remove it. - Re-run the full suite to confirm the fix didn't destabilize neighbors.
Gotchas
- Retry/skip as a fix. Masks the flake, ships the nondeterminism. Forbidden here.
sleepto dodge a race. Slows the suite and still flakes under load. Await the condition.- One green run = done. Flakes are probabilistic — verify with many randomized runs.
- Stabilizing a real product race. If the code races, fix the code, not just the assertion.
- Ignoring order/parallel dimension. Run isolated and in-suite; the bug hides in whichever you skip.
Companion commands
/absolute upgrade— a flaky suite makes upgrade verification unreliable; deflake first./absolute debt— flaky-test annotations are test debt; this clears them at the root./absolute work— when the flake is a genuine product-code race needing real design.
Files (absolute)
-
references
-
health-engine.md 5.3 KB
Loading…
-
-
README.md 660 B
# absolute-deflake Flaky test fixes. Detects nondeterministic tests empirically (repeat/shuffle/parallel runs), diagnoses the root cause (shared state, clock, network, concurrency), fixes it — never retries, skips, or sleeps. ## Quick Facts | Field | Value | |-------|-------| | Category | workflow | | Version | 0.5.0 | | Platforms | claude-code, gemini-cli, openai-codex, mcp | | License | MIT | ## How to Install ```bash npx skills add maddhruv/absolute-deflake ``` ## Usage ```bash /absolute-deflake "Fix the flaky tests in our CI" /absolute-deflake "This test fails randomly" ``` ## Maintainers - [@dhruvjainin](https://github.com/dhruvjainin) -
SKILL.md 4.9 KB
--- name: absolute-deflake version: 0.5.0 description: > Flaky test fixes: detect nondeterministic tests empirically (repeat/shuffle/parallel runs), diagnose the root cause, fix it — never retry/skip/sleep — and verify across many randomized runs. Triggers on "absolute deflake", "fix flaky tests", "CI is flaky", "this test fails randomly/intermittently". category: workflow tags: - workflow - testing - flaky-tests - maintenance platforms: - claude-code - gemini-cli - openai-codex - mcp user-invocable: true argument-hint: "[target]" license: MIT maintainers: - github: maddhruv --- > Start your first response with the 🧪 emoji. ## Absolute Deflake Find tests that pass and fail nondeterministically, diagnose the **root cause** of each, and fix it — not by retrying or skipping, but by removing the source of nondeterminism. Output is evidence (failure rate per test) → cause → fix, verified by repeated runs. Runs the shared engine in **`references/health-engine.md`** — read it for the DETECT → SCAN → TRIAGE → FIX → VERIFY → REPORT loop and the safety contract. This file covers only what's specific to flaky tests. --- ## When to use - "Our CI is flaky", "this test fails randomly", "fix the intermittent failures". - A test passes locally but fails in CI (or vice versa), or fails ~1 in N runs. - Burning down a backlog of `retry`/`skip`-marked tests that mask real flakiness. Not for tests that fail *deterministically* — that's a real bug or a real regression (`/absolute work` for a fix, or just fix it). `deflake` targets *nondeterministic* failures. --- ## What it scans Establish flakiness empirically — a test isn't flaky because someone said so. Use `preferences.health.deflakeRuns` from config as the default N for repeat-runs (else 20): | Ecosystem | Repeat-run / detect | |---|---| | Jest/Vitest | run suite N× (`--run` loop), randomize order (`--shuffle` / `testSequencer`) | | pytest | `pytest-randomly` + `pytest --count=N` (`pytest-repeat`); `-p no:randomly` to A/B | | Go | `go test -count=N -shuffle=on ./...`, `-race` | Also mine signals: existing `retry`/`flaky`/`skip` annotations, CI history if reachable, and run the suite both **in isolation** and **in full/parallel** — order- and concurrency- dependent failures only show one way. Record a **failure rate** per suspect test. --- ## Common root causes (diagnose, don't guess) | Cause | Tell | Fix | |---|---|---| | Test-order / shared state | passes alone, fails in suite (or vice versa) | isolate state; reset/teardown between tests | | Time / clock | fails near midnight, DST, or under load | fake timers / inject clock; no real `sleep` | | Async race / missing await | fails under parallelism or slow CI | await the actual condition; no fixed timeouts | | Randomness | fails ~X% with no pattern | seed the RNG; fix the seed in tests | | Network / external I/O | fails offline or on slow links | mock/stub the boundary | | Unordered collections | fails on map/set iteration order | sort before asserting | | Resource leak / port reuse | fails on repeat or parallel runs | unique resources; clean up | --- ## Risk ranking (TRIAGE) | Wave | Class | Default | |---|---|---| | 1 | clear, isolated cause (seed, await, fake clock, sort) | fix now | | 2 | shared-state / ordering — needs fixture refactor | fix this pass, per test | | 3 | flakiness pointing at a **real product race**, not just the test | gated — surface; may be a genuine bug to fix in code | A flaky test sometimes means the *code* has a race, not the test. Don't "stabilize" the test into hiding a real concurrency bug — flag wave-3 cases for a real fix. --- ## Fix & verify - Fix the **cause**. Then prove it: re-run the test **many times** (and shuffled / parallel / with `-race`) — green once is not deflaked; green across N randomized runs is. - Remove the `retry`/`skip`/`flaky` annotation that was masking it once the cause is fixed. - **Never** "fix" by adding retries, raising timeouts blindly, `sleep`, or skipping the test — that hides flakiness, doesn't remove it. - Re-run the **full** suite to confirm the fix didn't destabilize neighbors. --- ## Gotchas 1. **Retry/skip as a fix.** Masks the flake, ships the nondeterminism. Forbidden here. 2. **`sleep` to dodge a race.** Slows the suite and still flakes under load. Await the condition. 3. **One green run = done.** Flakes are probabilistic — verify with many randomized runs. 4. **Stabilizing a real product race.** If the *code* races, fix the code, not just the assertion. 5. **Ignoring order/parallel dimension.** Run isolated *and* in-suite; the bug hides in whichever you skip. --- ## Companion commands - **`/absolute upgrade`** — a flaky suite makes upgrade verification unreliable; deflake first. - **`/absolute debt`** — flaky-test annotations are test debt; this clears them at the root. - **`/absolute work`** — when the flake is a genuine product-code race needing real design.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.