principle-test-behavior-not-implementation
De la autor
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.
Instalare
npx skills add backnotprop/pstack --skill principle-test-behavior-not-implementation -a claude-code
Se instalează în .claude/skills/principle-test-behavior-not-implementation/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 90
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- 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.Testare★ 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.Testare★ 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.Testare★ 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.Testare★ 59
- test-driven-developmentmvschwarz/openrigUse when implementing any feature or bugfix, before writing implementation codeTestare★ 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.Testare★ 118
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te