TestNeo
TestNeo Docs Developer documentation
Documentation

Build with TestNeo, your way.

Release Intelligence from your IDE, plus SDK, CLI, and MCP — one platform for PR risk, test signals, and ship confidence.

Start here

Release Intelligence

Validate PRs from Cursor, VS Code, or GitHub — PASS / WARN / BLOCK, execute impacted tests on PR, Engineering Memory, release gate, and outcome learning.

  • Full business flow: ingest → patterns → validate → gate → outcomes
  • 15-minute customer demo script (web + MCP)
  • Copy-paste prompts EM1–EM9, C17–C25 · GitHub @TestNeo validate
  • Unified patterns with Worsening/Stable trend
  • Outcome learning + read-only calibration
Release Intelligence guide →
AI agents

AI Agent Verification

Wire CrewAI, LangGraph, or custom agents to TestNeo — post-run golden tests, PR validation, and release gates via MCP.

  • Generate → persist → execute (same UI as VS Code + MCP)
  • Post-agent verification hook (MCP + REST)
  • PASS / WARN / BLOCK on PRs + release bundle
Agent verification guide →
For developers

Playwright AI SDK

Write Playwright tests in plain English, keep full Playwright control, and publish runs to TestNeo from your CI.

  • ai.run, ai.step, ai.api in one file
  • Hybrid mode: NLP + native page.click()
  • Strict / balanced / adaptive modes for CI
  • Guest mode — try without an API key
Read SDK docs →
For your whole team

MCP AI Agent

Add TestNeo to Cursor, VS Code, or any MCP client. Generate, run, watch, and triage from one thread.

  • One flow: generate → run → watch → triage
  • Plain-language answers for every role
  • Writes need your confirmation (on by default)
  • Failures: cause + rerun plan in chat
  • 68 MCP tools · mega-tool C25 · EM1–EM9 · execute on PR
Read MCP docs →
For product & GTM

VS Code Extension

What TestNeo supports in VS Code today, how extension + MCP workflows fit together, and how teams move from code change to release confidence.

  • Source code → impact → validation workflows
  • Planning-only vs executed stage explained clearly
  • Positioning language for customers and field teams
  • Architecture map: Extension + MCP + Playwright + backend
Read VS Code docs →
Terminal & CI

TestNeo CLI

Run .testneo flows from your shell or pipeline — same projects, API key, and dashboard.

  • testneo run with --wait for CI
  • Same NLP format as the VS Code extension
  • testneo doctor validates your setup
  • GitHub Actions env vars documented
Read CLI docs →

Quick links

CLI Quickstart SDK Quickstart Release Intelligence Engineering Memory flow Workflow 7 — PR validate Patterns & trend GitHub @TestNeo validate Outcome learning Workflow 8 — Engineering Memory Workflow 10 — Ship loop MCP Quickstart VS Code Extension Guide MCP Tool Reference SDK API Reference MCP Workflows MCP Customer playbook MCP Prompt Packs EM prompts (EM1–EM9) MCP Web AI Assistant Try the Playground