targeted-testing
选择并运行最小的正确验证步骤(检查→按路径的聚焦Jest→更广泛的测试套件)。每当您修改代码并需要快速获得信心时使用。
📖 中文导读:选择并运行最小的正确验证步骤(检查→按路径的聚焦Jest→更广泛的测试套件)。每当您修改代码并需要快速获得信心时使用。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: targeted-testing description: Pick and run the smallest correct validation step (checks → focused Jest by path → broader suites). Use whenever you modify code and need confidence quickly.
Targeted Testing
Scope
- Select the smallest test/check that proves the change
- Prevent slow, flaky, or irrelevant test runs
- Capture evidence in session notes
Inputs
- Files changed
- Whether the change is UI server / CLI / DB adapter / crawler
- Existing check scripts near the code
Procedure
- Prefer a local check script first (fast, deterministic, exits cleanly).
- Then run the smallest Jest suite by path.
- Only then widen to broader suites if needed.
- Record the exact commands and outcomes in
WORKING_NOTES.md.
If you need browser semantics but don’t want full Jest E2E yet, prefer the single-browser scenario runner:
node tools/dev/ui-scenario-suite.js --suite=scripts/ui/scenarios/<suite>.suite.js --scenario=001 --print-logs-on-failure
Validation
- Official Jest invocation rule (repo policy): use
npm run test:by-path <file>.
Escalation / Research request
Ask for dedicated research if:
- there is no obvious “smallest check” and you need a new check harness
- the feature spans multiple systems and you need a validation ladder proposal
References
- Testing quick reference:
docs/TESTING_QUICK_REFERENCE.md - Validation ladder guidance:
AGENTS.md