TestNeo
TestNeo Docs VS Code documentation
Product-facing guide

TestNeo for VS Code: supported today and how the flow works

This page explains what TestNeo supports in VS Code today, how the end-to-end IDE flow works, and how extension UI, MCP/agents, and backend orchestration connect into one verification model.

Short version: TestNeo supports VS Code today and supports other IDE clients (such as Cursor, Windsurf, Kiro, and cloud dev environments) through the same MCP + backend model. This page focuses on VS Code, and the core message is: TestNeo turns your IDE into a software verification workspace.
source code → test creation → code change impact → impacted-only validation → result review

What “VS Code support” means in TestNeo

1) Extension-native workflows Sign-in, project access, generation, execution, and result review directly in IDE surfaces.
2) MCP / AI-assisted workflows Agents in VS Code can plan, generate, validate, execute, triage, and explain outcomes using TestNeo tools.

These are not two separate products. They are two surfaces over the same backend and verification model.

What we support today in VS Code

  • Sign in to TestNeo and connect to account-backed projects
  • Connect workflows to project environments
  • Create test cases from source code, app context, or existing context
  • Review generated cases before execution
  • Run tests from IDE
  • Detect impacted tests from code changes
  • Validate PR or diff with impacted-only planning
  • Execute impacted tests when write-enabled execution is configured
  • Review summaries, logs, failures, and linked results
  • Update NLP and rerun
  • Export or preview Playwright-oriented output

What makes this different

Traditional plugins help record steps, run tests, and show raw output. TestNeo helps teams understand code, understand change, identify impact, run the right validation, and decide what is safe to ship.

Supported VS Code workflow map

  • Open repo in VS Code
  • Connect TestNeo project
  • Create or review tests from code and context
  • Make a code change or open a PR
  • Find impacted tests and flows
  • Run only relevant validation
  • Review findings and results
  • Update tests, fix issues, rerun, or approve

Detailed flows

1) Source code to test creation

Open repo, connect project, analyze code/context, generate candidate tests, review NLP steps, edit, save, execute. Value: source code becomes verification input, not just AI text output.

2) Code change to impact analysis

After code changes, TestNeo reads diff/commit/PR context and predicts impacted tests. Good output is a relevant set of impacted flows, not a large unfiltered list.

3) PR validation and impacted-only execution

TestNeo returns changed files, impacted flows, impacted tests, planned validation stages, and release summary. If execution is enabled, it moves into run status and final outcomes.

Planning-only stage

  • tests = queued
  • execution_mode = planned_only
  • Impact layer is working, execution has not started

Execution stage

  • execution_mode = executed
  • Tests move to running, passed, failed, or partial

4) Run, observe, and review in VS Code

Run test/batch/impacted set, watch progress, inspect summary and failure logs, open linked views for deeper triage, then rerun or approve.

5) Failure to fix loop

failure → understanding → update → rerun

This reduces manual guesswork and shortens debug loops.

6) Playwright and engineering-friendly output

Teams can generate/refine in TestNeo and export Playwright-oriented scripts for engineering control and pipeline continuity.

What extension messaging should say

Core message: TestNeo helps teams understand what to verify, not just execute more tests.

Use language like

  • Generate validation from your code
  • Find impacted tests for this change
  • Run only what matters
  • Review release risk before merge
  • Inspect failures and next actions

Avoid weak positioning

  • Record and run tests
  • A faster automation plugin
  • Another Playwright helper
Recommended framing: TestNeo for VS Code is an AI-native verification workspace for code changes.

Architecture view: how pieces fit

One backend, multiple IDE surfaces:

  • VS Code extension: direct product UI
  • MCP tools: agent / AI interface
  • Playwright SDK: engineering execution surface
  • Backend orchestration: shared verification engine

This enables the same journey via UI actions, AI prompts, and backend-driven automation without rebuilding logic in each channel.

What is true today vs what depends on configuration

Available today

  • Project access and account-backed workflows
  • Test generation and test review flows
  • Code-change impact identification
  • PR validation planning
  • Execution visibility and result review
  • Failure triage flows

Requires correct configuration

  • Write-enabled execution from AI/MCP flows
  • Impacted-only execution from PR validation
  • Local app validation where local agent/routing is required
  • Stable impact quality where project mappings and inventory are incomplete

The strongest customer story

A developer changes code in VS Code. TestNeo understands the change, predicts impacted flows and tests, generates or updates the right validation, runs only what matters, and returns a clear release signal without blind regression runs.

Suggested positioning lines

  • Know what changed. Verify what matters.
  • From source code to release confidence, inside VS Code.
  • TestNeo turns VS Code into a verification workspace, not just a test runner.
  • Generate from code. Validate by impact. Ship with confidence.

Last updated: May 2026 · TestNeo Docs