principle-test-behavior-not-implementation
From the author
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
Install
npx skills add backnotprop/pstack --skill principle-test-behavior-not-implementation -a claude-code
Installs to .claude/skills/principle-test-behavior-not-implementation/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 90
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- implementhashgraph-online/awesome-codex-pluginsChange or repair code, config or services without weakening tests; report what ran and what did not. Use when: implementing a change or fixing a defect.Testing★ 1.4K
- write-testsdzhng/skillsWrite tests that pin real behavior instead of implementation details, config values, or lucky samples. Use when adding tests for new behavior, writing a regression test, fixing a brittle or flaky test, reviewing a test diff, or when a test breaks after a refactor or config change that didn't change behavior.Testing★ 1.4K
- test-driven-executionomergocmen/vibe-coder-kitBefore writing any implementation code, define the acceptance criteria and test cases that the code must satisfy. Agents then write code to pass these tests — not to match a vague description. Eliminates "it works on my machine" and "I think this is what you wanted" outcomes.Testing★ 98
- regression-testingnahid-sparktales/agent-dispatcherTurn a fixed bug into a test that fails on the old code and passes on the new one. Assert behavior at the cheapest useful level and compare old behavior without reverting unrelated work or leaving scratch files. Use after a fix or when recurring defects lack coverage; not for a new feature's test strategy or an environmental/cosmetic failure.Testing★ 59
- test-driven-developmentmvschwarz/openrigUse when implementing any feature or bugfix, before writing implementation codeTesting★ 8.3K
- verifying-acceptance-criteriajaktestowac/awesome-copilot-for-testersCompares implementation evidence against acceptance criteria and shows what is met, partial, missing, or untestable. Use when checking feature readiness, preparing QA sign-off, or turning criteria into a concrete verification matrix without inventing missing behavior.Testing★ 118
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in