Generate a complete test suite satisfying the 8-section test contract.

The framework automatically:

• Detects language and framework from source code

• Generates tests for happy path, failure paths, and boundary cases

• Validates every test against the 8-section contract before returning

• Builds a traceability matrix linking tests to requirements

• Identifies coverage gaps and makes recommendations

Validate a test or test suite against the 8-section contract.

Use this to check any existing test — generated or hand-written — for compliance. The contract requires all 8 sections: Test ID, Why Generated, Requirement Mapping, How it Exercises, Coverage Contribution, Expected Outcome, Gaps, Meaningfulness Check.

Analyze the coverage of a test suite and identify gaps.

Build a requirements-to-tests traceability matrix.

Analyze code/requirements and suggest which test types to apply.

Detect programming language and test framework from source code.

Health check for the Universal Test Framework MCP server.

Returns server status, version, and uptime. Suitable for use as a Docker HEALTHCHECK command, Kubernetes liveness/readiness probe, or basic availability verification.

Returns: status : "ok" when the server is healthy version : UTF semantic version string uptime_s : seconds the server process has been running tools : number of registered MCP tools

Query the UTF persistent test registry.

Execute test files and return structured results with CI annotations.

Execution is always optional — controlled by UTF config. Never blocks generation.

Run mutation testing on a source+test file pair and return coverage metrics.

Supports mutmut (Python), Stryker (JS/TS), PIT (Java), and gremlins (Go). The adapter is auto-detected based on language and tool availability.

Get UTF feedback loop status: gap analysis, coverage health, trend, and delta requirements.

Import JUnit XML execution results into the UTF registry.

Use this when you have already run tests with pytest / Maven / Go and want to register the results so that generate_report shows real pass/fail rates.

Generate the 8-section contract compliance report (Tool #12).

Reads test records and execution results from the registry, builds the contract report in the requested formats, and returns report paths + summary.

Parse test files and register per-method 8-section contract records.

This is the UTF registration bridge — it reads LLM-written test files, extracts the per-method 8-section comment blocks, and upserts status=generated rows into the UTF registry. Without this step, generate_report has no Per-Test Contract Detail cards.

IMPORTANT — Phase 1, Step ③ of the UTF 3-phase workflow: ① generate_tests (scaffold) ② Write real test methods with per-method TC-{PRJ}-{MODULE}-{NNN} blocks ③ register_contracts ← this tool ④ generate_report (verify contract detail cards) ⑤ pytest --junit-xml=... ⑥ import_test_results ⑦ generate_report (now shows both contract cards AND execution results)