免费在 GitHub 公开中文介绍

test-audit

检查新旧测试实际保护的行为和可检测的缺陷，审视重复检查及对实现细节的依赖。删除前整理依据，保留必要验证，并清理仅供测试使用的代码。

原文查看原文说明

Writing/changing/reviewing/sweeping tests: reject duplicate or implementation-coupled proof; remove test-only production seams.

适用场景

test-audit检查软件测试实际保护的内容，帮助判断是否应新增测试，以及如何整理已有测试。检查范围包括外部可观察的行为、能够检测的缺陷、与现有测试的重复，以及仅为测试公开的函数等。删除前会记录检测能力、保留的验证、历史背景和风险，留下必要的测试。

适合整理不改变行为却导致测试失败的代码，或处理相似测试不断增加的情况。它还会检查防止缺陷再次出现的回归测试，确认其在修复前是否因预期原因失败。对于运行缓慢或检查源代码的测试，也会判断其独立验证价值，不会仅凭这些特点删除。

资料中的验证流程以OpenClaw环境为前提，并引用Vitest、仓库内的验证脚本及相关技能。整理整个子系统前，需要阅读CAMPAIGN.md。调查从只读检查开始，提交和创建PR等操作须获得授权后进行。

本介绍由 AI（OpenAI Codex）根据公开的 SKILL.md 撰写。准确的规格请查看下方原文。

AI 仅根据 SKILL.md 的内容，从 4 个方面进行了评估。星标数和热度不计入评估。

总分按每项 A=25 分、B=15 分、C=5 分相加。由 AI（OpenAI Codex）于 2026年10月19日评估。仅供参考，安装前请同时查看原文。

如果您认为评估有误，请申请复核

安装前可以查看交给 AI 代理的指令内容。

Authoring gates every new/changed test.
Audits: remove low-value proof in coherent owner batches; never chase deletion counts.
Whole-subsystem campaign: read CAMPAIGN.md first.

Before adding test, answer:

Protected observable behavior, invariant, or independent contract?
Credible regression that makes it fail?
Why existing proof misses it? Each contract: one primary owner at strongest boundary. Another layer needs distinct transport/lifecycle risk. Extend tables/shared fixtures; consolidate repeated setup.
Export, flag, wrapper, injection hook with no production caller needed? Move proof to real boundary instead.

Use boundary and cost guide.
Regressions must fail pre-fix for intended reason, pass after repair; report unavailable baseline proof.
One owner regression covers bug; never replay at every crossed layer.
Behavior-preserving refactors should not break test.

Reject self-comparisons, copied inventories, source greps, implementation/call-shape assertions, duplicate contracts, test-only seams, subject-generated expected values, mocks supplying asserted behavior.
Fixtures must not fabricate owner receipts/order or claim persistence path never writes.
Negative controls must fail at intended guard; names must match exercised behavior.
Auditing candidates: use full checklist.

Keep independent API, SDK, protocol, config, migration, storage, security, platform, default, prompt-byte, generated-language, package, release, architecture, observable-ordering contracts. Static/slow ≠ disposable.
Source inspection must survive identifier-only refactors and guard independent user-facing contract.
Baseline failures may be bugs to repair, not tests to delete.

Before audit edit: read candidate evidence and workflow; inspect full owners/callers/history; record remaining proof before deletion.
Delete obsolete production seams with tests; never optimize for deletion counts.
Follow proof policy; preserve active Vitest checkouts; run owner/sibling proof + changed checks; then autoreview.
Report causes, retained contracts, proof/cost, production versus test LOC, follow-ups. Commit/push/land only with task authority.

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。