Documentation
Build with TestNeo, your way.
Three developer surfaces, one platform. SDK in your repo, CLI in your shell, MCP in your IDE — or use them together.
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.apiin one file -
Hybrid mode: NLP + native
page.click() - Strict / balanced / adaptive modes for CI
- Guest mode — try without an API key
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
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
TestNeo CLI
Run .testneo flows from your shell or pipeline — same projects, API key, and dashboard.
-
testneo runwith--waitfor CI - Same NLP format as the VS Code extension
-
testneo doctorvalidates your setup - GitHub Actions env vars documented