사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/mdsmithaustin/pstack --skill principle-test-behavior-not-implementation시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Test Behavior, Not Implementation
A test calls the code as its users do and asserts the exact result they see. Rewrite or delete any test that would still pass if every imported function returned undefined or a wrong value.
These shapes fail that check:
- Loose or no assertion:
toBeDefined,toBeTruthy,not.toThrow,toBeGreaterThan(0). - Call or absence only:
toHaveBeenCalled,not.toHaveBeenCalled,toBeUndefined,toEqual([]). - Expected value computed by the code under test:
expect(f(a)).toBe(f(a)). - Restated constant, config default, table row, or prompt string.
- Assertions on data the test built, with no call to the subject.
Fix: call the subject in the test body with one concrete input and assert the literal output or effect. For a mock, assert the payload it received. For an absence, also assert the presence on another input. For a constant, test the mechanism that reads it with one input instead of restating the value.
Keep relation checks across table rows (a key in two tables, a parent that exists) and *.test-d.ts type checks.
Production prerequisites. An acceptance test must not pass because its setup establishes state or ordering that production never establishes. Exercise the real initialization path or prove that the caller supplies the prerequisite. Ordinary fixture inputs that real callers can supply are valid.
Notation, not a runtime. Write Given, When, Then or Gherkin-style tests in the project's existing framework. Do not add Cucumber, a Gherkin runner, or .feature files unless the project already runs one or the user explicitly asks for Cucumber, a runner, or .feature files. A request for Gherkin-style tests is not such a request.
