Find what a feature's tests are missing

coverage.gap_for_featureReadsOnly looks things up; never changes your workspace.

What it does

Checks which kinds of testing a feature or user story has no test cases for yet. Every active test case of the suite and of the user stories and sub-features under it (inactive cases are skipped) is sorted into one of 8 facets by keyword matching on its title and description, with no AI involved; a case that matches no keyword counts as happy-path. The 8 facets: happy-path (the normal success flow, e.g. "user resets password and logs in"); edge cases (boundaries, e.g. "empty email field" or "maximum length name"); error / recovery (failures and retries, e.g. "network drops during payment, retry succeeds"); permissions (wrong or missing login, e.g. "a viewer cannot delete a project"); accessibility (e.g. "the form can be completed with the keyboard only"); performance (e.g. "search returns in under 1 second with 10,000 items"); browser matrix (e.g. "date picker works in Safari"); data-shape mutations (unexpected API data, e.g. "a missing field in the response does not crash the page"). Returns totalCases, perFacet counts, missingFacets, missingAcLabels (gaps in the AC1, AC2, … numbering, e.g. AC1 and AC3 exist but not AC2), existingCases and a suggested next prompt. Read-only. Next: fetch the find-coverage-gaps prompt with prompts/get (pass this whole result as JSON in its feature argument), create the proposed cases with case.create_batch, then fill them in via ac-to-testcase.

Ask your agent

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

  • “What kinds of tests is the checkout feature missing?”
  • “Did we forget to test permissions or error cases for password reset?”
  • “Are there gaps in the acceptance criteria for this user story?”

Inputs

NameTypeDescription
featureId
required
stringId of the suite to check: a feature, sub-feature or user story id (from feature.list, feature.implement or userstory.create). Must belong to the connected workspace. Cases in its child user stories and sub-features count too.

The MCP call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "coverage.gap_for_feature",
    "arguments": {
      "featureId": "<featureId>"
    }
  }
}

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.