Expert software testing: unit/integration/e2e, TDD, test doubles, fixtures, and flakiness. Trigger keywords: testing, unit test, integration test, e2e, TDD, mock, stub, fake, spy, fixture, coverage, flaky test, assertion, test pyramid, snapshot. Use for writing tests, designing test strategy, or fixing flaky/brittle/slow tests.
How this skill is triggered — by the user, by Claude, or both
Slash command
/testing-expert:testing-expertThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> Test behavior, not implementation — that's what survives refactors. Fast and deterministic beats exhaustive. A bug fixed without a failing test first will come back.
Test behavior, not implementation — that's what survives refactors. Fast and deterministic beats exhaustive. A bug fixed without a failing test first will come back.
llm-testing-expert.debugging-expert.performance-expert.returns 401 when token expired).await real conditions instead of sleep, control async ordering, isolate test data. Quarantine and fix flaky tests — don't retry-until-green.Red (write a failing test for the next behavior) → Green (simplest code to pass) → Refactor (clean up with the test as safety net). Especially valuable for bug fixes: reproduce as a failing test first.
sleep() to wait for async → flaky and slow; await a condition/event.Behavior test with a controlled boundary (pytest)
def test_token_expires(monkeypatch):
clock = {"now": 1000}
monkeypatch.setattr(auth, "now", lambda: clock["now"]) # fake the clock
token = auth.issue(ttl=60) # valid until 1060
assert auth.is_valid(token)
clock["now"] = 1061 # advance time deterministically
assert not auth.is_valid(token) # asserts behavior, not internals
Bug → failing test first
def test_discount_never_negative(): # reproduces the reported bug
assert price(items=[], coupon="HUGE") == 0 # was returning -5
debugging-expert — turn a bug into a failing test, then fix.refactoring-expert — tests are the safety net for restructuring.github-master — run tests + coverage gates in CI.llm-testing-expert — evaluation for LLM systems.Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.
npx claudepluginhub miaoge-ge/coding-agent-skills --plugin testing-expert