behavioral-testing

Plugin behavioral-testing from marketplace mdlockyer-plugins in mdlockyer/code-quality-plugins. Commands read from the repo's manifest — 2 days ago.

Skills (4)

• behavioral-unit-testing

  Write tests that can actually fail — expected values from the spec, not from running the code; evidence the test fails on the bug and not only passes on the fix; no silent changes to tests; no satisfying the check instead of the request. Use whenever writing, fixing, strengthening, or reviewing test

• bug-repro

  Turn a bug report, issue, failing scenario, or suspected defect into a fail-to-pass reproduction test with proof that it fails on the current code for the right reason and would pass on any correct fix. Use when asked to "reproduce this bug", "write a failing test for this issue", "prove this is bro

• test-audit

  Audit a test suite for tests that cannot fail, tests that pass on the bug, tests that enforce wrong behavior, tests pinned to one implementation, and flaky tests; prove each finding with a surviving mutant; report with coverage and stop for approval. Use when asked to audit, review, grade, or assess

• test-repair

  Repair tests that a test audit found weak, flaky, pinned to one implementation, or suspicious, with proof for every change: a surviving mutant that now dies, a revert that now goes red, or a shuffled run that now agrees. Use after a test audit when the user approves findings, or when asked to \"fix

Subagents (5)

• oracle-writer

  Derives expected values for tests from the specification, docstrings, type signatures, callers, issue text, and hand arithmetic, without reading the implementation under test, so that the expectation is independent of the code's current behavior. Dispatched by test-repair before any test is rewritte

• test-auditor

  Examines one test file during a test audit, running five single-question lenses one at a time (can't fail; would pass on the bug; enforces suspicious behavior; pinned to one implementation; brittle or flaky) and recording candidates with file:test_name, the line, and what the test should assert inst

• test-prover

  Proves or disproves a test-audit candidate by breaking the production code the test guards (flip a comparison, move a boundary, delete a branch, return a constant), running the test, recording whether it stayed green, and restoring the code; also proves repairs by showing the recorded mutant now die

• test-repairer

  Rewrites one approved test-audit finding into a test that can fail, using expected values derived by the oracle-writer and the oracle ladder's rewrite patterns, preserving the project's conventions, one behavior per test, and recording before/after with the derivation of every literal. The only role

• test-verifier

  Adversarially verifies test-audit findings and test repairs with fresh context: re-reads every cited line, checks whether another test already catches the recorded mutant, whether the mutant is equivalent, whether a "suspicious" expectation is actually the spec, whether a repaired test fails on the

Hooks (2)

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}"/hooks/scripts/passing_test_reminder.py

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}"/hooks/scripts/test_edit_guard.py

Similar plugins