From wf
Testing philosophy — what good tests look like, anti-patterns, coverage priorities, naming
How this skill is triggered — by the user, by Claude, or both
Slash command
/wf:common-testing-kThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Knowledge skill** — Testing philosophy, coverage priorities, naming conventions, anti-patterns.
Knowledge skill — Testing philosophy, coverage priorities, naming conventions, anti-patterns.
Tests define behavior. Reading the test suite should tell you what the system does without reading the implementation.
Given/When/Then structure. Names read as behavior descriptions:
Tests that lie — mocking the thing being tested, assertions that assert nothing, tests changed to match broken behavior.
Tests that waste — testing implementation details, testing that the language works, excessive mocking that disconnects from reality.
Tests that mislead — skipped tests with eternal TODOs, names that don't match what they test, failure messages that don't help debug.
npx claudepluginhub jsai23/claude-tooling --plugin wfUse when writing tests, designing test strategy, or reviewing test coverage. Covers test pyramid, naming, mocking, and flaky test policy.
Provides a checklist for writing and reviewing tests: naming tests/files, designing data/fixtures/mocks, choosing assertions. Use for unit/integration/E2E tests.
Provides testing strategies including test pyramid, TDD/BDD, unit/integration/E2E patterns, mocking strategies, test data factories, snapshot testing, and mutation testing. Use for designing test strategies, writing tests, or improving coverage.