testing-reliability
/testing-reliability
Diagnose flaky tests, misleading mocks or fakes, sleep-based waits, brittle fixtures, test-only production hooks, weak assertions, and mutation-testing gaps. Use when CI behavior differs, tests hide defects, or coverage creates false confidence.
- Author
- aeondave ↗
- Repository
- malskill ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/find_polluter.py
What it does and when to use it
Diagnose flaky tests, misleading mocks or fakes, sleep-based waits, brittle fixtures, test-only production hooks, weak assertions, and mutation-testing gaps. Use when CI behavior differs, tests hide defects, or coverage creates false confidence.
Original author description
Diagnose flaky tests, misleading mocks or fakes, sleep-based waits, brittle fixtures, test-only production hooks, weak assertions, and mutation-testing gaps. Use when CI behavior differs, tests hide defects, or coverage creates false confidence.
How it works
- When to activate
- Reliability workflow
- Anti-patterns to remove
- Offensive testing focus
- Resources
SKILL.md preview
--- name: testing-reliability description: "Diagnose flaky tests, misleading mocks or fakes, sleep-based waits, brittle fixtures, test-only production hooks, weak assertions, and mutation-testing gaps. Use when CI behavior differs, tests hide defects, or coverage creates false confidence." license: MIT compatibility: "Language-agnostic testing guidance. Pair with python-testing, c-testing, cpp-testing, golang-testing, rust-testing, or asm-testing for concrete commands." metadata: author: AeonDave version: "1.3" --- # Testing Reliability Make tests detect the behavior they claim to cover and make failures attributable. Use this skill to repair the test signal; `test-driven-development` owns the test-first implementation loop. ## When to activate - Flaky, timing-sensitive, or order-dependent tests. - Heavy mocks, unclear patch targets, or fakes that do not match real behavior. - Production code changed only to make tests easier. - Coverage increased without stronger assertions. - Surviving or uncovered mutants in behavior that matters. - CI failures that cannot be reproduced locally. ## Reliability workflow 1. Identify the claimed behavior and the misleading result. Preserve the failure evidence or demonstrate a missed defect with the smallest relevant test selection; a local pass does not invalidate a CI failure. 2. Investigate the relevant source of uncertainty: assertions, test doubles, fixture lifecycle, time, randomness, filesystem/network state, locale, order, or concurrency. Use `systematic-debugging` when failure attribution or the product defect remains unclear. 3. Correct that cause. Strengthen an assertion, isolate/reset owned state, repair synchronization, or replace an inaccurate double as needed; do not apply every technique to every test. 4. Check sensitivity to the defect and preservation of valid behavior. For a double, check the part of the collaborator's contract that matters; choose a real dependency, fake, stub, or mock according to the test's scope and control needs. 5. Run focused checks and relevant broader tests. Repeat or vary order/schedules when investigating a flake, with a bounded diagnostic purpose; do not rerun until a convenient green result hides failures. Use `verification-before-completion` for final coverage and freshness. ## Anti-patterns to remove - Testing incidental internal calls instead of the required behavior or interaction contract. - Partial mocks that silently omit important side effects. - Sleeping for async behavior instead of waiting on a condition. - Shared mutable fixtures that couple tests by order. - Golden outputs updated without reviewing semantic changes. - Coverage-only tests that assert nothing meaningful. ## Offensive testing focus - Exploit harnesses must prove primitives, not just crash/no-crash. - Fuzz reproducer tests must pin seed/input and minimized artifact. - Network tooling tests should use captured transcripts, local test servers, or protocol fakes. - Evasion tests must distinguish telemetry absence from collection failure. ## Resources Load on demand: - [references/testing-anti-patterns.md](references/testing-anti-patterns.md) — load when diagnosing mock/timing failures, coverage without useful assertions, or mutation results. Scripts: - `scripts/find_polluter.py` — runs matching test files separately and reports the first that leaves a watched filesystem path present. It does not detect in-memory state, changes to existing files, or interactions requiring a sequence of test files; inspect command failures before interpreting a clean result.
Files in this package (3)
- SKILL.md 4 KB
- references/testing-anti-patterns.md 5 KB
- scripts/find_polluter.py 5 KB
Versions
The database has no other skills named testing-reliability.
Database snapshot: 13.11.2026 · package version 27c122b5108e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ae-ltd-mutation-gate
Use when unit tests look green but confidence is low and mutation testing is needed to expose weak assertions. AE.LTD workflow for targeted mutation runs and actionable test hardening. - 100review-testing
Review test code for quality, design, and completeness after implementing a feature or fixing a bug. Use when the user asks to "review my tests", "check my test quality", "are these tests good enough", "review testing", or after completing a feature implementation that includes… - 100testing-audit
Audit the test suite for coverage gaps, test quality, flaky tests, and strategy alignment. Use when assessing test health before a release, or when tests feel weak, slow, or flaky. - 90better-testing
Review and improve how tests protect critical software behavior. Use when assessing missing unit, integration, contract, or end-to-end coverage; flaky tests; weak assertions; happy-path-only tests; excessive mocking; implementation-coupled tests; low-value snapshots; slow… - 90testing
Pragmatic testing guidance focused on confidence, behavior over implementation details, and integration-first coverage. Use when designing a test strategy, writing or reviewing tests, reducing brittle mocks, or deciding what is worth testing in an application or library. - 95testing-anti-patterns
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing…