Testing Engine
Plan required suites, run/validate evidence, scaffold missing tests before commit.
What you will learn
- testing_plan paths
- testing_validate
- testing_enforce
Prerequisites
Surface
| MCP | testing_plan · testing_run · testing_validate · testing_diff · testing_enforce · testing_scaffold |
|---|
What this feature does
Testing Engine maps changed paths to suiteIds / vitest paths. Agents must run those suites; testing_enforce refuses commit evidence gaps.
How to call it
Call these MCP tools through your AGS / tower-gov host — testing_plan, testing_run, testing_validate, testing_diff, testing_enforce, testing_scaffold.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.
- testing_plan
- testing_run (or local vitest)
- testing_validate
- testing_enforce
{ "paths": ["packages/app/src/auth/session.ts"] }Scaffold
When coverage is missing, testing_scaffold creates planted-fault capable stubs — then you must fill assertions that can fail.
{ "paths": ["packages/app/src/auth/session.ts"] }What success looks like
Plan lists concrete vitest paths
testing_validate ok after runs
Common failure modes
Validate without running listed suites
Scaffold then skip execute
Broad path set → under-specified plan