agentleFS
Sn4kyGitSn4kyGit/qa-agent-blueprint/.claude/skills/test-reliability/SKILL.md

test-reliability

Skill2 starsChanged 7 days agoApache-2.0View on GitHub

Runtime per-test healing with evidence: multi-attribute selector healing, environment-aware diagnosis, flake classification, quarantine management, confidence-scored auto-repair. Use when: flaky test, test stability, self-healing locator, broken locator recovery, unreliable test, quarantine flaky test. Not for bulk selector regeneration after a refactor or CI failure clustering.

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. About 0 are common, 15 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check the project bridge file .agents/qa-project-context/<KEY>.md first — it carries known flaky areas, selector strategy, and CI …

    line 36
  2. Distinctive:

    What is your current flaky test rate?: Check CI failure stats over the last 30 days.

    line 38
  3. Distinctive:

    Healing must be observable and reviewable: Every automated repair produces evidence: what broke, what was tried, what worked, the …

    line 49
  4. Distinctive:

    Flaky tests are bugs: Not annoyances to tolerate.

    line 53
  5. Distinctive:

    Self-healing is a spectrum: Start with resilient locators (Level 1), add fallback strategies (Level 2), then environment-aware healing …

    line 57
  6. Distinctive:

    Not all test failures are test problems.

    line 74
  7. Distinctive:

    When an action fails, check backend health before blaming the test:

    line 78
  8. Distinctive:

    Before declaring a test failure in CI, check for resource contention:

    line 88
  9. Distinctive:

    Diagnosis: If either check fails, classify as an environment issue and annotate the test result.

    line 92
  10. Distinctive:

    Test data expires, gets cleaned up, or becomes invalid.

    line 96
  11. Very specific:

    Use testInfo.testId in email/identifiers for per-test uniqueness.

    line 126
  12. Very specific:

    Always clean up in the fixture's post-use block, not in afterEach — fixtures guarantee cleanup on failure.

    line 128
  13. Distinctive:

    After applying a repair, verify the test still exercises the same user intent:

    line 195
  14. Distinctive:

    Maximum quarantine age: 14 days: After 14 days, fix it or delete it.

    line 243
  15. Distinctive:

    Every quarantine entry has a ticket link: No anonymous quarantines.

    line 244
  16. Distinctive:

    Weekly review: Check the quarantine list every sprint.

    line 245
  17. Very specific:

    After fixing, prove stability: npx playwright test <spec> --repeat-each=50 --workers=4 — require 50/50 passes, in CI conditions too.

    line 294
  18. Distinctive:

    Every flaky test is identified and categorized by root cause (timing, data dependency, environment, etc.).

    line 300
  19. Distinctive:

    Every quarantine entry has a ticket reference and an expiry date <= 14 days out.

    line 304

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<objective> A retried test that still flakes will eventually fail 3-of-3 during your most critical release, and a silently auto-repaired test may now verify a different element entirely. This skill builds suites teams can trust: resilient locators, classified flakes, environment-aware healing, data healing, and observable repair with confidence scoring — every automated fix produces evidence a human can review. </objective>

Quick Route

SituationGo to
Test flakes in CI, root cause unknownFlake Classification → decision tree
Locator broke, want resilient replacementLocator Resilience
Action fails, suspect slow backend not UI bugEnvironment-Aware Healing
401/404/429 mid-test from stale dataData Healing
Want auto-repair with review gateObservable Repair Workflow
Isolate a flaky test without blocking CIQuarantine Management
Step-by-step triage of one flaky testreferences/flaky-test-runbook.md

Discovery Questions

Check the project bridge file .agents/qa-project-context/<KEY>.md first — it carries known flaky areas, selector strategy, and CI environment details. Skip any question it already answers.

  • What is your current flaky test rate? Check CI failure stats over the last 30 days. Below 2% is healthy; 2-5% needs attention; above 5% is eroding team trust.
  • Where is the pain concentrated? Locator breakage? Timing? Test data? Environment? If unknown, instrument first (see Flake Classification).
  • What is your current selector strategy? data-testid everywhere, mixed CSS and role-based, or no strategy (whatever works)? This sets the stability-score baseline.
  • How do you handle flaky tests today? Retry and hope, skip and forget, or something structured? Decides how much process you need to add.
  • What CI environment runs the tests? Same machine every time or different runners? Consistent or variable resources? Drives the environment-vs-test diagnosis.
  • What is your test data strategy? Shared database, per-test fixtures, factory seeding, or external services? Decides whether data healing applies.

Core Principles

  1. Prevention over cure. Writing a resilient test costs 1x. Investigating a flaky one costs 10x. Losing team trust in the suite costs 100x.
  2. Healing must be observable and reviewable. Every automated repair produces evidence: what broke, what was tried, what worked, the confidence score. Silent fixes erode trust as fast as silent failures.
  3. Classify before fixing. The fix for a timing issue is completely different from the fix for a data dependency. Wrong diagnosis wastes effort and can make things worse.
  4. Flaky tests are bugs. Not annoyances to tolerate. A flaky test either has a test bug (fix the test), reveals an app bug (fix the app), or exposes an environment issue (fix the environment).
  5. Track reliability as a metric, not a feeling. Measure flaky rate, mean time to heal, quarantine age, and selector stability. What gets measured gets fixed.
  6. Self-healing is a spectrum. Start with resilient locators (Level 1), add fallback strategies (Level 2), then environment-aware healing (Level 3), then confidence-scored auto-repair (Level 4). Do not jump to Level 4 before mastering Level 1.

Locator Resilience & Flake Classification

Locator healing: multi-attribute selectors (data-testid + role + text), DOM similarity matching, and selector stability scoring. Prefer semantic attributes over CSS classes.

Flake classification (first hit wins): environment (infra/build), data (state leakage, ordering), timing (race conditions, async), selector (DOM change), product (real bug). Use the decision tree to classify before fixing.

Full selector strategies, similarity matching, and the classification decision tree: references/locator-and-classification.md.

Environment-Aware Healing

Not all test failures are test problems. Some are environment problems. Environment-aware healing distinguishes the two and adapts.

Slow Backend vs True UI Failure

When an action fails, check backend health before blaming the test:

  1. Action fails → Hit /api/health.
  2. Backend unhealthy (5xx or timeout) → Retry with exponential backoff. Diagnose as backend_down. This is not a UI bug.
  3. Backend healthy (2xx) → This is a real UI/test failure. Do not retry.

Return a structured diagnosis: { success: boolean; diagnosis: 'backend_down' | 'ui_failure' | 'backend_slow_recovered' }. This feeds flake classification — backend issues are environment issues, not test bugs.

Resource Contention Detection

Before declaring a test failure in CI, check for resource contention:

  • Browser health: Load about:blank. If it takes > 2s (baseline < 500ms), the runner is overloaded.
  • API health: Hit /api/health. If it takes > 5s (baseline < 1s), the backend is under pressure.
  • Diagnosis: If either check fails, classify as an environment issue and annotate the test result. Do not count resource-contention failures toward flaky test rates.

Data Healing

Test data expires, gets cleaned up, or becomes invalid. Data healing detects and regenerates stale test data.

Common Data Failure Patterns

PatternSignalFix
Expired auth token401 response during testRegenerate token in fixture
Deleted test record404 when accessing seeded dataRe-seed before test
Uniqueness violation409 or constraint errorGenerate unique identifiers per run
Stale cacheWrong data returnedClear cache in setup
Exceeded quota429 or rate limit errorReset quotas or use dedicated test account

Self-Healing Test Data Fixture Pattern

Build fixtures that verify data exists and regenerate if stale.

// Pattern: verify → heal → use → cleanup
testUser: async ({ request }, use, testInfo) => {
  // 1. Try to find existing test user by deterministic email
  // 2. Verify auth token is still valid (GET /api/me)
  // 3. If token expired → refresh it (POST /refresh-token), mark as healed
  // 4. If user missing → create new one, mark as healed
  // 5. If healed → annotate testInfo for observability
  // 6. use(user) → run the test
  // 7. Cleanup: delete test user (guaranteed by fixture, even on failure)
}

Key patterns:

  • Use testInfo.testId in email/identifiers for per-test uniqueness.
  • Annotate testInfo.annotations when healing occurs, for observability.
  • Always clean up in the fixture's post-use block, not in afterEach — fixtures guarantee cleanup on failure.

Observable Repair Workflow

Core guardrail: Healing must be observable and reviewable. Every repair follows this flow:

Failure Detected
  │
  ▼
Candidate Repair Generated
  │
  ▼
Confidence Score Computed (0.0 - 1.0)
  │
  ▼
Evidence Diff Produced (what changed, what was tried)
  │
  ▼
Approval Policy Applied
  │ ├── Score >= 0.9   → Auto-apply, log for batch review
  │ ├── Score 0.7-0.89 → Apply in quarantine, flag for individual review
  │ ├── Score 0.5-0.69 → Do NOT apply, open PR with evidence for review
  │ └── Score < 0.5    → Discard, manual investigation required
  │
  ▼
Intent Fidelity Check (does repaired test still test the same thing?)
  │
  ▼
Rollback if intent fidelity drops

Confidence Scoring

Score each repair candidate on six dimensions (weighted sum, 0.0-1.0):

DimensionWeightScoring
Match specificity0.30testId=1.0, role=0.9, text=0.7, context=0.5, CSS=0.3
Element visible0.151.0 if visible, 0.0 if not
Same parent container0.151.0 if same container, 0.0 if different
Same element type0.151.0 if same tag+role, 0.0 if different
Text similarity0.150.0-1.0 (Levenshtein ratio of accessible name)
Attribute overlap0.100.0-1.0 (Jaccard of shared attributes)

Score thresholds (half-open bands — 0.9 belongs to the auto-apply tier only):

  • >= 0.9 — Auto-apply, log for batch review.
  • 0.7-0.89 — Apply in quarantine, flag for individual review.
  • 0.5-0.69 — Do not apply; open a PR with evidence for review.
  • < 0.5 — Discard, manual investigation required.

references/flaky-test-runbook.md (Score Interpretation) uses these exact four bands — keep all three locations identical if you edit them.

Repair Evidence

Every repair produces an evidence record containing: test file, test name, failure type, original locator, candidate replacements (each with confidence, evidence string, and intent-preserved flag), which candidate was selected, timestamp, approval path, rollback trigger, and a screencast.webm recording of the repair run (Playwright 1.59+ page.screencast with showActions annotations — the "agentic video receipt"). Without the screencast, a Level-3/4 healed test asks reviewers to trust a JSON record; with it, the diff and the runtime are both inspectable. In this blueprint the record lands in the run's evidence directory (evidence/<KEY>/<TICKET>/<ts>/); durable flake knowledge (root cause, stable alternative) belongs to memory/learnings/flaky-tests.md via retro-learn.

Buy vs Build

Hand Levels 3-4 to a vendor when you don't want to own a confidence-scored healer; build in-house when you need on-prem/air-gapped deployment, an explicit AI-prompt audit trail, or quarantine logic your tracker can't express. Building stops being worth it once a hosted tool already fingerprints + clusters + auto-quarantines for you.

  • For Selenium / Selenide / Robot Framework suites, Healenium remains the dedicated self-healing layer (now on AWS Marketplace).
  • For agent-driven self-healing in Playwright, Playwright MCP is the canonical path — it gives the agent live browser control to discover replacement locators when CLI + skills isn't enough.
  • Hosted platforms shipping this workflow: Trunk Flaky Tests (auto-quarantine + AI failure clustering; its 2026 Quarantined Tests API returns the current quarantine list programmatically — same hygiene workflow this skill builds by hand), CloudBees Smart Tests (formerly Launchable; agents searching old docs may find the old name), and Datadog Test Optimization (renamed from "Datadog Test Visibility" in December 2024). All three offer fingerprinting + clustering + auto-quarantine that maps onto Levels 3-4.

Intent Fidelity Checking

After applying a repair, verify the test still exercises the same user intent:

  • Element type changed (e.g. button → a) — intent NOT preserved, rollback.
  • ARIA role changed (e.g. button → link) — intent NOT preserved, rollback.
  • Form action changed (targets a different endpoint) — intent NOT preserved, rollback.
  • Same tag, role, and form action — intent preserved, keep repair.

A repair that changes WHAT the test verifies (not just HOW it finds elements) must be rolled back.

Quarantine Management

Quarantine isolates flaky tests so they run but do not block CI. See references/flaky-test-runbook.md (Step 6) for the full config and CI wiring; the essentials:

// Tag the flaky test
test('intermittent WebSocket reconnect', {
  tag: ['@quarantine'],
  annotation: {
    type: 'quarantine',
    description: 'Flaky since 2026-03-15. Race condition in WebSocket handler. Ticket: BUG-1234.',
  },
}, async ({ page }) => { /* ... */ });
// playwright.config.ts — separate projects
projects: [
  { name: 'stable', testMatch: /.*\.spec\.ts/, grep: /^(?!.*@quarantine)/ },  // exclude quarantine
  { name: 'quarantine', grep: /@quarantine/, retries: 3 },
],

In CI, run --project=stable as a blocking step and --project=quarantine with continue-on-error: true so the quarantine project never blocks the pipeline.

Quarantine Lifecycle

1. DETECT    — Test identified as flaky (CI reporter or manual triage)
2. TAG       — Add @quarantine annotation with ticket link and date
3. ISOLATE   — Quarantine project runs separately, does not block
4. DIAGNOSE  — Follow the flaky test runbook (references/flaky-test-runbook.md)
5. FIX       — Apply the fix pattern for the classified category
6. VERIFY    — Run 50x with --repeat-each, zero failures required
7. RELEASE   — Remove @quarantine tag, add annotation documenting the fix

Quarantine Hygiene Rules

  • Maximum quarantine age: 14 days. After 14 days, fix it or delete it. Permanent quarantine is permanent rot.
  • Every quarantine entry has a ticket link. No anonymous quarantines.
  • Weekly review. Check the quarantine list every sprint. Aging quarantines get escalated.
  • Track quarantine size. More than 5% of tests in quarantine signals a systemic problem requiring process change, not just test fixes.

Anti-Patterns

1. Silent Selector Replacement

Replacing a broken selector with no logging, review, or confidence scoring. The repaired test may now verify a different element entirely. Every repair must produce evidence.

2. "Just Retry It" as a Fix

Retries are a detection mechanism, not a fix. A test that needs retry 2-of-3 will eventually fail 3-of-3 during your most critical release.

3. Disabling Flaky Tests Permanently

test.skip('flaky, will fix later') — "later" never comes. Either quarantine with tracking or delete entirely. Skipped tests with no ticket are dead code.

4. Treating All Flakiness the Same

Timing issues and data dependencies need completely different fixes. Adding waitForTimeout(5000) to a data-dependency problem makes the test slower and still flaky.

5. waitForTimeout as a Stability Fix

// NEVER the right fix
await page.waitForTimeout(5000);

// Wait for the actual condition
await expect(page.getByRole('table')).toBeVisible();
await page.waitForResponse(resp => resp.url().includes('/api/data') && resp.status() === 200);

6. Healing Without Observability

Auto-repair that produces no logs, evidence, or confidence scores. You cannot improve what you cannot measure, and you cannot trust what you cannot review.

7. Over-Engineering Healing Before Writing Stable Tests

Building a complex self-healing framework before adopting basic resilient-locator patterns. Start with multi-attribute selectors and proper waits. Add healing infrastructure only when data shows where breakage occurs.

8. No Quarantine Expiry

Tests sit in quarantine for months. Quarantine is a temporary state, not a permanent home. Enforce a 14-day maximum.

Failure Modes

SymptomLikely causeFix or check
Backend health check itself flaps → false backend_down diagnosisHealth endpoint is itself flaky/slowTrack the health endpoint's own p99 separately; don't gate diagnosis on a single probe
Artifact storage balloons after enabling repair videopage.screencast recording on every run, not just repairsRecord only on the repair path, not the happy path
Auto-repair accuracy drops below 80%Confidence threshold too low, or intent-fidelity check skippedRaise the auto-apply floor; never skip the intent check
Quarantine project blocks the pipelineMissing continue-on-error on the quarantine CI stepAdd it; the quarantine project must never block merges

Verification

  • Reproduce the flake: npx playwright test <spec> --repeat-each=20 --workers=4 --trace=on — it must fail at least once before you trust any fix.
  • After fixing, prove stability: npx playwright test <spec> --repeat-each=50 --workers=4 — require 50/50 passes, in CI conditions too.
  • Confirm quarantine routing: npx playwright test --project=stable excludes @quarantine tests and --project=quarantine runs only them.
  • Confirm selector audit emits numbers: the stability report lists a score per locator and a suite average.

Done When

  • Every flaky test is identified and categorized by root cause (timing, data dependency, environment, etc.).
  • Each flaky test is quarantined or fixed — no test silently retried without a documented plan and ticket reference.
  • selector-stability.md (or the CI report) lists a stability score per locator and reports a suite average >= 3.5.
  • The flaky-test-rate metric (% of tests passing on retry) is published to the CI dashboard and visible to the team.
  • Every quarantine entry has a ticket reference and an expiry date <= 14 days out.

Related Skills

  • test-automation — full Playwright/WebdriverIO setup, fixtures, and CLI-runner integration that the patterns here build on; bulk selector regeneration after a planned UI refactor happens there, this skill heals one test at runtime.
  • qa-metrics — track flaky rate, mean-time-to-heal, quarantine size, and selector stability over time.
  • failure-analysis — when flake investigation reveals a real app bug, the failure goes back to failure-analysis for classification (product-defect) and then to bug-report.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.