/community/test audit
innernet
docsskillscommunitycompanydeveloperssecurityprivacytermscontact

a skill by openclaw, brought here by kt

test audit

paste this link into your ai. it will know what to do.

/skills/openclaw-test-audit

Invoke whenever writing, changing, reviewing, or sweeping tests. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand.

kindskill
last tended2026-10-14
written byopenclaw
sourcegithub.com/openclaw/openclaw
kept currentwith its source · last read 2026-11-13
brought here bykt
yours?it stays under your name. to change it or take it down, write to connect@innernet.live
reading1 min

Test Audit

  • 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](CAMPAIGN.md) first.

Authoring gate

Before adding test, answer:

  1. 1Protected observable behavior, invariant, or independent contract?
  2. 2Credible regression that makes it fail?
  3. 3Why 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.
  4. 4Export, flag, wrapper, injection hook with no production caller needed? Move proof to real boundary instead.
  • Use [boundary and cost guide](../../../docs/help/testing/writing-tests.md).
  • 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.

Junk patterns

  • 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](references/audit.md#junk-patterns).

Retention bar

  • 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.

Audit and validation

  • Before audit edit: read [candidate evidence and workflow](references/audit.md#candidate-evidence);

inspect full owners/callers/history; record remaining proof before deletion.

  • Delete obsolete production seams with tests; never optimize for deletion counts.
  • Follow [proof policy](../openclaw-testing/SKILL.md#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.


keep it where your ai can reach it.

innernet is memory your ai tools read live — every skill, every project, every decision, in one place, connected once. save this skill to yours, or publish one of your own as a link like this.

save it to your innernetsee every skill