免费在 GitHub 公开
what-to-test
Use when writing tests, improving coverage, or deciding what to test in this CLI
中文简介正在准备中。当前显示原文说明。
查看安装方法包含的文件（1）
- SKILL.md1.1 KB
SKILL.md（原文）
安装前可以查看交给 AI 代理的指令内容。
What to Test
Philosophy
Test user-facing behavior. If a user would notice it's broken, it needs a test.
All CLI commands must be tested - including commands marked "internal". Internal commands are still user-facing (Matt uses them daily).
What Makes a Good Test
- Tests behavior users depend on
- Validates real workflows, not implementation details
- Catches regressions before users do
Do NOT write tests just to increase coverage numbers. Use coverage as a guide to find untested user-facing behavior.
What NOT to Test
Use /* v8 ignore start */ for:
- Integration boundaries (actual git calls, shell execution, filesystem)
- Service layers that get mocked in tests
- Entry points and DI wiring
- Boilerplate, unreachable error branches
Testing Pattern
- Export a
runX()function from command files for testability - Mock external services (GitService, PromptService)
- Test error paths users will actually hit
- Use v8 ignore for CLI formatting/presentation code
评价
还没有评价。欢迎分享你的使用感受。
评论
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。