Release Intelligence — setup & end-to-end

The intelligence lifecycle

Teams with few tests today: start with MCP Customer E2E (generate → run), then return here for PR validation.

What is a release verification?

One release verification (RV) = one PR validation workflow:

1. Impact analysis on changed files
2. Risk score (0–100) and PASS / WARN / BLOCK
3. Optional impacted test execution
4. Evidence, fix plan, and PR comment draft

Each run is stored at /web/pr-validation/<workflow_id> — share the link in GitHub or Slack.

Setup — MCP in your IDE

1. Account & API key

Sign up → Settings → API keys (tn_…).

2. Cursor mcp.json

{
  "mcpServers": {
    "testneo": {
      "command": "npx",
      "args": ["-y", "@testneo/mcp-server"],
      "env": {
        "TESTNEO_BASE_URL": "https://app.testneo.ai",
        "TESTNEO_API_KEY": "YOUR_API_KEY",
        "TESTNEO_MCP_ALLOW_WRITE": "false"
      }
    }
  }
}

Set TESTNEO_MCP_ALLOW_WRITE to true only when you want test execution inside validation.

3. Verify

In chat: Validate my TestNeo connection or call testneo_validate_connection.

4. IDE playbooks (auto-behavior)

Clone or copy from the TestNeo repo: Cursor uses .cursor/rules/testneo-pr-validation.mdc; VS Code Copilot uses .github/copilot-instructions.md — they auto-detect git context and call testneo_pr_validation_workflow first.

Full install steps: MCP Quickstart.

End-to-end checklist (PR focus)

Greenfield (no tests yet)? Run Customer E2E first, then repeat from step 4 on every PR.

Prompt techniques (copy-paste)

Replace <PROJECT_ID> and <PR_NUMBER> with your values. More prompts: MCP Prompt Packs — PR Validation.

Validate PR <PR_NUMBER> for project <PROJECT_ID>.
Use git to detect base_sha, head_sha, and changed_files.
Call testneo_pr_validation_workflow with confirm false.
Show PASS/WARN/BLOCK, risk score, top findings, and the PR comment draft.
Give me the workflow_id link to the web board.

I'm modifying [list files] in project <PROJECT_ID>.
What's the historical failure rate and flakiness on related tests?
Have we seen BLOCK-level PRs on these paths recently?

Explain why this PR is blocked — root cause per finding.
Then give me the NOW/NEXT fix plan and which tests to rerun.

Is project <PROJECT_ID> ready to release to production?
Give me release confidence and a Go / No-Go verdict with top risks.

Show recent PR validation history for project <PROJECT_ID> —
what's the risk trend over the last two weeks?

Web UI (same data as MCP)

• PR Validation board — /web/pr-validation
• PR detail — /web/pr-validation/<workflow_id>
• Branch health — Analytics → Branch (CI + PR risk overlay)
• Release readiness — confidence score and ship checklist

Tool reference and JSON contracts: PR Validation & Release Confidence.

Plans & limits

Errors: release_verification_limit_reached (monthly RV cap) or MCP 403 (daily write cap on Free). See MCP troubleshooting — limits.

Related documentation