testing
Guide test design when adding, changing, or reviewing tests, especially mock boundaries and test infrastructure. Not a requirement to audit existing tests or add a separate testing phase.
来源信息
- 仓库
- ilude/dotfiles
- 最近来源活动
- 2026年9月7日 23:38
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 4
- Forks
- 1
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- testing
- description
- Guide test design when adding, changing, or reviewing tests, especially mock boundaries and test infrastructure. Not a requirement to audit existing tests or add a separate testing phase.
# Testing
- Prefer tests of observable behavior using existing test infrastructure.
- Use mocks when real dependencies would be unsafe, nondeterministic, or impractical. Mocks are not inherently a problem.
- Do not mock away the behavior under test. Assert internal call sequences only when those interactions are part of the required behavior.
- Do not build abstractions or extensive fake infrastructure for speculative tests.
- Choose tests for required behavior, demonstrated defects, and credible risks in the changed path. Do not expand coverage merely because another case can be imagined.
- Passing mocked tests proves only what they exercise; do not present them as evidence that real integrations work.
在 GitHub 查看