Test Maze for engineering leads

Govern agents without slowing them.

Turn on spec-based development and every coding agent on the team works inside the same rules: no edit until it declares the story it is implementing, no commit without a Testmaze-Ref, and CI re-checks the range. The traceability matrix shows requirement → acceptance test → work item → commit → verdict → release for every story, exportable for the auditor.

Start free Watch the workflow

SOUND FAMILIAR?

What goes wrong today

No way to mandate a spec

Rules files and plan modes are suggestions. Nothing stops an agent from editing code that no story asked for.

No independent signal

The agent says tests pass. The tests, the results and the verdict all come from the same place that wrote the code.

Tooling fragmentation

Every agent on the team runs tests differently. There is no one surface to hold them all to the same standard.

WITH TEST MAZE

What changes

No story, no edit

spec.status · spec.start_work · PreToolUse hook

With the policy on, the Claude Code hook blocks file edits until the agent has declared a reviewed story for the branch. The server rejects stories with no acceptance cases or that are not Ready.

No reference, no commit

commit-msg hook · spec check-range

Every commit carries a Testmaze-Ref trailer naming the story or case; the git hook adds and checks it, and the CI range check fails the build on an untraced commit.

The chain, on one page

Traceability · spec.trace

Requirement → acceptance test → work item → commit → verdict → defects → release, one row per story, with CSV export. The audit trail ISO 9001 / 12207-style processes ask for.

Independent verification by design

testmaze-verifier · recordedBy

The verifier runs as a separate subagent and every recorded result says who recorded it. Verdicts come from fixed rules, pinned to the commit.

Built for your perimeter

tmt_* tokens · BYOK · TESTMAZE_MCP_URL

Per-workspace tokens isolate every team, bring-your-own AI keys are AES-256-GCM encrypted, and a private deployment keeps the whole loop inside your network.

SEE IT MOVE