Skip to content

testing.md

Latest commit

 

History

History
8 lines (7 loc) · 647 Bytes

testing.md

File metadata and controls

8 lines (7 loc) · 647 Bytes
Raw

Testing conventions

  • Prefer behavior-focused tests over implementation details.
  • Arrange–Act–Assert; one primary assertion per test when practical.
  • Mock only at system boundaries (network, clock, filesystem); prefer real implementations elsewhere.
  • After code changes, run the narrowest test that proves the fix (file or suite), not the whole repo unless needed.
  • Do not skip or delete failing tests to “go green”—fix or mark explicit pending with reason.
  • When preflight/skill reports sandbox: ready and the repo documents compose tests, verifier may accept sandbox exec logs as equivalent evidence to local test runners.