Skip to content

Testing

Tests must prove consumer or agent value.

Weak tests check marker strings or file existence. Strong tests cross the next meaningful boundary: validation, normalized contracts, import/adoption, generated output compile, runtime smoke, or an explicit unsupported diagnostic.

Terminal window
npm test
Terminal window
bash ./scripts/verify-engine.sh
bash ./scripts/verify-cli-package.sh

verify-engine.sh is engine-scoped. Release-facing changes use the broader preflight:

Terminal window
npm run release:preflight

The release preflight runs docs/RAG checks, root Topogram validation, strict SDLC validation, secret scanning, engine verification, and packed CLI smoke.

Terminal window
npm run smoke:test-app

smoke:test-app writes .tmp/smoke-test-app and must run the generated starter’s verification surface after generation.

Documented command shapes should execute in tests or be clearly marked as environment-dependent.