사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/alexbruno/dev-skills --skill verification-and-testing시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Verification & Testing
Never claim a change works, passes, or is complete without fresh, direct verification evidence collected after the final edit.
Core Rule
Evidence before completion claims. If you did not run a check after your last change and observe its output, do not report it as passing.
1. Align Verification with workflow/SPEC.md
- Map every acceptance criterion in
workflow/SPEC.mdand the verification strategy inworkflow/PLAN.mdto a concrete check (automated test, build, lint, typecheck, or explicit runtime check). - Treat untested acceptance criteria as incomplete work.
2. Write Meaningful Tests
- Test behavior, not implementation details: Assert observable outputs, state transitions, and side effects so tests survive safe refactoring (
code-simplification). - Cover the edges: Include boundary values, empty/null inputs, invalid states, and error paths—not just the happy path.
- Keep tests isolated and deterministic: Avoid shared mutable state, real network calls, or time-dependent flakiness unless explicitly testing integration boundaries.
- Never weaken assertions: Do not relax, skip, or mock away the core behavior under test just to make a suite green.
3. Execution Gate After Final Edit
Before handing off work or moving to workflow/REVIEW.md:
- Run the relevant unit/integration tests, linter, typechecker, and build commands.
- Confirm all executed checks pass with zero skipped or relaxed assertions.
- Report the exact scope of what was run (e.g., full suite vs. targeted subset, any environment limitations).