adewale

Testing Best Practices — Testing skill for Claude Code

Testing community

A Claude Code skill for enforcing testing best practices: TDD, property-based testing, real objects over mocks, test quality assessment, and anti-pattern detection.

How to install Testing Best Practices

This entry records only its repository, not the path inside it, so there is no exact command to give. Open adewale/testing-best-practices and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Testing Best Practices does

A Claude Code skill for enforcing testing best practices: TDD, property-based testing, real objects over mocks, test quality assessment, and anti-pattern detection.

Alternatives in Testing

AI Contribution Skills (Engram) — branch-pr: clean branch and PR workflow 2.5k ★
Claude Codepro — by Max Ritter - Professional development environment for Claude Code with spec-driven workflow, TDD enforcemen 1.6k ★
Loki Spec Status — Check whether the spec has drifted from its lock using Loki's living-spec drift detection, and summarize the r 1.1k ★

README

testing-best-practices

[![skills.sh](https://skills.sh/b/adewale/testing-best-practices)](https://skills.sh/adewale/testing-best-practices)

An agent skill that enforces testing best practices when writing, reviewing, or improving tests. Built from 25 research documents covering real-world testing patterns across 16 GitHub accounts, three engineering organizations, books, and long-form testing literature; grounded in practitioner work from Kent Beck (TDD) to TigerBeetle (deterministic simulation), Jane Street (expect tests), Ward Cunningham (Fit/customer examples), Salvatore Sanfilippo / antirez (Redis-style differential fuzzing and testability seams), and an analysis of the Google Testing Blog's feed-enumerated 404-post archive (test sizes, flake data, mutation testing at scale, the test-double canon; raw batch artifacts were not retained).

![A typographic ledger of the sixteen testing techniques this skill teaches, organised into three tiers — Always (Unit, Smoke, Regression); When triggered (Property-based, End-to-end, Doc/Code sync, Contract, VCR cassette, Characterization, Differential, Golden file, Pirate/Conformance); With caution (Visual/Screenshot, Mutation, Performance, Fuzz). A top strip frames the red-green-refactor rhythm: a test that fails first, the smallest code that passes, clean up while green.](research/diagrams/skill-ledger.png)

What it does

When an agent uses this skill, it produces higher-quality tests than it would on its own. Specifically:

Property-based tests appear (Hypothesis, fast-check, proptest) where broad input spaces need more than examples
Assertions get stronger: meaningful behavior/state/error checks replace toBeDefined(), truthy/not-empty checks, and logs
Error-handling paths are exercised with injected downstream failures instead of only invalid-input tests
Concurrency contracts are pinned with contention-driving tests and race-detector guidance rather than observational t.Log output
**Bet