Retire a regression baseline

regression.unfreeze_runChanges dataCreates, updates or deletes something in your workspace.

What it does

Unfreezes a test run so its cases no longer have to keep passing. A regression baseline is a frozen run whose tests every later pdlc.verify requires to be present and passing. Use it only when the baseline is deliberately out of date, for example the feature was removed or rebuilt; do not use it just to get a failing verdict to pass. Ask the user before calling it. Requires a reason. Takes effect immediately for every later pdlc.verify in the workspace; you can freeze the run again with regression.freeze_run. Returns success and the reason; a run that was not frozen returns alreadyUnfrozen: true. Call regression.list_frozen first to find the right run.

Ask your agent

You don’t call regression.unfreeze_run yourself. Say something like this to Claude Code, Cursor or another MCP-connected agent:

  • “We removed the old checkout, stop requiring its tests to pass”
  • “Retire the baseline from before the redesign”

Inputs

NameTypeDescription
testRunId
required
stringId of the frozen test run to unfreeze: an id from regression.list_frozen. Must belong to the connected workspace.
reason
required
stringWhy this baseline no longer applies, 8 to 500 characters, e.g. "Legacy checkout removed in v2". Saved on the run (unfreezeReason, with unfrozenAt and unfrozenBy) so the decision can be reviewed later.

The MCP call

What the agent’s MCP client sends (placeholders in angle brackets):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "regression.unfreeze_run",
    "arguments": {
      "testRunId": "<testRunId>",
      "reason": "<reason>"
    }
  }
}

Connect your agent

npx -y @testmaze/mcp init tmt_xxx
claude mcp add tm --scope project -- npx -y @testmaze/mcp

Create the token in your Test Maze workspace under Settings → MCP. Setup for Cursor, Cline, Gemini CLI and Codex CLI is shown there too.