testing

testing

A Claude Code plugin for the test stage of a disciplined dev workflow. Plan what needs testing, author tests at the right level, verify the running app end-to-end, and diagnose failures to root cause. Five skills, one concern: proving behavior with tests.

Skill	What it does
/testing:plan	Coverage-gap analysis. Classify changed files by required test type, identify gaps, prioritize by regression risk.
/testing:write	Test authoring discipline. Vertical-slice TDD, test-type selection, naming, placement, fixture patterns, four-pillars assessment.
/testing:run-e2e	Live app verification. Start the app via the project's orchestrator, drive UI/API flows with token-efficient browser automation, capture evidence; includes a non-UI smoke-test playbook (MCP stdio handshake, shell/PowerShell surfaces).
/testing:diagnose	Failing-test diagnosis. Failure classification, root-cause analysis (never retry blindly), then the reproduce → isolate → fix → retest → regression loop.
/testing:audit	Can't-fail test detection, a deterministic script finds assertion-free bodies, self-identical (recomputed-expectation) assertions, and mock-only oracles across JS/TS, Python, and C#; reports with a coverage denominator, gates fail-closed via --check, and opt-in persists findings for a review fix pass.

Works in any repo

• Reads your conventions, assumes none. Test frameworks, project locations, naming, fixture patterns, and the e2e-orchestrator configuration come from your own project's CLAUDE.md / rules and existing test projects; the skills infer from what exists when nothing is documented.
• Cross-plugin refs degrade gracefully. Test invocation defers to the toolchain plugin's /toolchain:check when installed and to the project's own test command otherwise; TDD design questions route to /tdd:principles, browser mechanics to /playwright:playwright, outcome sign-off to /verification:confirm, and the implement loop to /implementation:implement. Each is used when installed and substituted with inline guidance or a manual handoff when absent. No step blocks on a missing plugin.
• Self-contained. Test-type tables, the E2E evidence contract, the non-UI smoke-test playbook, and diagnosis loops ship inside the plugin and are referenced via ${CLAUDE_PLUGIN_ROOT}.

Install

/plugin marketplace add melodic-software/claude-code-plugins
/plugin install testing@melodic-software

Configuration

Test structure and conventions come from your own project's CLAUDE.md and rules. This plugin declares no userConfig options.

/testing:run-e2e reads one optional consumer-project config surface, .claude/testing/e2e.md: recording (video | gif | off, default off) and browser_mode (headed | headless, default headless). Both defaults preserve current behavior, so the file is optional. Its keys, defaults, and precedence are documented in the skill's bundled run-e2e/context/e2e-config.md; it layers per the marketplace config-cascade convention.

License

MIT (SPDX-License-Identifier: MIT).