Generate and run MCP Rigor tests

​

Before you begin

​

Generate natural-language tests

1. Open Test Automation and select MCP Rigor as the framework.
2. Select the source requirement and include its approved MCP tool, resource or prompt contract, input arguments and expected behavior.
3. Generate the review-only package. Browser page objects and journeys are not required.
4. Review the generated .mcpr natural-language suite and its assertions.
5. Approve the package before execution. Existing YAML suites remain supported.

MCP Test 1
Suite: "MCP discovery smoke test"
MCP URL: ${env.MCP_URL}
Server options:
  headers:
    Authorization: "Bearer ${env.MCP_TOKEN}"
Test: "Discover available tools"
  List all tools
  Expect it succeeds

​

Execute and review evidence

1. Configure protected parameters MCP_URL and MCP_TOKEN; do not paste tokens into requirements, source code or reports.
2. Use a public HTTPS Streamable HTTP endpoint on port 443. Ensure the short-lived OAuth or bot token remains valid for the run.
3. Review the hosted-worker budget and credit consent where metering is enabled.
4. Execute the approved suite through the configured LoopIQ runner.
5. Review execution counts and sanitized JSON evidence. Link the run to the relevant release using the existing evidence workflow.

• Test automation
• Credit usage