write-a-unit-test
Write a focused deterministic unit test that specifies one behavior, boundary, failure, or invariant with useful diagnostics. Use when a small code unit can be verified without production dependencies.
소스 정보
- 저장소
- protosphinx/sphinxstack
- 최근 소스 활동
- 2026년 7월 29일 13:55
- 감지된 SKILL.md 언어
- 영어
- 스타
- 3
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- write-a-unit-test
- category
- code
- description
- Write a focused deterministic unit test that specifies one behavior, boundary, failure, or invariant with useful diagnostics. Use when a small code unit can be verified without production dependencies.
# write-a-unit-test
Test observable behavior, not implementation trivia.
## When to use
- Use for pure logic or a bounded component with controlled collaborators.
- Do not call live networks, shared databases, clocks, randomness, or secrets from a unit test.
## Procedure
1. State the behavior and why unit scope is appropriate.
2. Choose the public input and output or state change to observe.
3. Create the smallest representative setup with explicit clock, randomness, filesystem, or collaborator control.
4. Exercise one behavior per test and name it as a readable specification.
5. Assert meaningful values, errors, side effects, and invariant boundaries.
6. Add null, empty, minimum, maximum, invalid, and alternate-path cases where relevant.
7. Run the test against the unfixed behavior when addressing a defect.
8. Run it repeatedly and with the nearby suite, then simplify any brittle fixture.
## Done
- A unit test file specifies the target behavior, boundaries, controlled dependencies, and useful assertions
- The test is verified to fail for the intended defect and pass deterministically with the accepted behavior
GitHub에서 보기