Frequently asked questions
What Test Maze is, how your agent connects to it, how a verdict is decided, what we store and what it costs. Something missing? Ask us.
The basics
What is Test Maze?
Test Maze is the verifier for AI coding agents. Your agent writes the code and runs the tests; Test Maze keeps the features, user stories and test cases, records every result against the exact git commit, and returns a deterministic pass or fail verdict.
Why does an agent need a verifier?
Because an agent that writes the code, writes the tests and reports the result is grading its own homework. Test Maze holds the test estate and the grading separately, so a pass is something you can point at: these cases, this run, this commit.
Is Test Maze a replacement for my test framework?
No. Keep Playwright, Jest, pytest or whatever you use. Test Maze records what those tests are meant to cover and what happened when your agent ran them, then grades the outcome.
Do I have to be an engineer to use it?
You need a coding agent and a project. You describe features and fixes in plain English; the agent calls the tools. Everything it does is visible in the app on the Agent Sessions page.
Connecting your agent
How do I connect my coding agent?
Create an MCP token in your workspace under Settings → MCP, run "npx -y @testmaze/mcp init <token>" in your project folder (it stores the token in .env.testmaze, which is git-ignored), then register the server with your agent — for Claude Code, "claude mcp add tm --scope project -- npx -y @testmaze/mcp".
Which coding agents are supported?
Any Model Context Protocol client. Setup instructions in the app cover Claude Code, Cursor, Cline, Gemini CLI and Codex CLI, and the same stdio server works anywhere else MCP is supported.
Do I call the tools myself?
No. You ask in plain English — "write test cases for the password reset flow", "verify this change" — and the agent picks from the 55 tools and fills in their inputs.
Can several people share a workspace?
Yes. Invite teammates from Settings → Team Management; each person gets a role, and every agent session in the workspace is visible to the team.
Verdicts and quality
How is the pass/fail verdict decided?
By fixed rules over the recorded results: pass when at least one case passed and none failed, fail when a case failed or a frozen regression-baseline case is missing or failing, otherwise in-progress. Waived acceptance criteria are excluded from the tally.
Is AI involved in the verdict?
No. The verdict path is deterministic — the same results always produce the same verdict. AI may only compose an optional hint about what to fix next.
What happens after a fail?
The verdict carries a next step: repair the code, repair the test, add coverage, or ship. Your agent reads it and continues the loop without you having to translate.
What are frozen baselines and waivers?
Freezing a test run turns its cases into a regression baseline: if one of them later goes missing or fails, the verdict fails. A waiver marks an acceptance criterion as deliberately not covered yet, with a reason, so it does not silently drag the verdict down.
Data and security
Does Test Maze read my source code?
No. Test Maze never clones, scans or indexes your repository. It receives only what your agent sends in a tool call: test artefacts, run results, git identifiers (sha, branch, clean working tree), optional screenshots, and a code snippet when you explicitly ask for a code-quality check.
What is stored about my test runs?
The cases, their results, who or what recorded them, and the git sha, branch and working-tree state of the commit under test. That provenance is what makes a verdict checkable later.
Where do my AI provider keys live?
If you bring your own OpenAI, Gemini or GMI Cloud key, it is stored AES-256-GCM encrypted at rest and used only for your workspace’s calls. It is never shown back to the browser and never leaves the server.
Can I see everything my agent did?
Yes. The Agent Sessions page lists every tool call in the workspace with its inputs, results and timing, so nothing an agent does is invisible to the team.
Plans and billing
Is there a free plan?
Yes — Basic is free forever and includes the whole verifier loop. Pro is $19.99 per month (or $215.88 a year, about 10% off) for teams. See the pricing page for details.
What are AI credits?
Credits pay for AI work that runs on Test Maze provider keys, at $2 per million tokens, topped up in packs of 5M, 10M or 25M tokens. Bring your own provider key and that usage bills to your provider instead.
How do I get help?
Write to us from the contact page and we reply by email. Pro workspaces get priority.
Looking for a specific tool? Every one of the 55 MCP tools has its own page under Tools.
Ready to give your agent a verifier?
Create a free workspace, generate an MCP token and connect your coding agent in under five minutes.