AI-Native Release Assurance Platform

AI can generate code. TestNeo helps you trust the release.

Understand what changed. Verify what matters. Know when to ship.

TestNeo creates a unified Release Intelligence Layer across code, requirements, Jira stories, Figma designs, APIs, user behavior, and execution evidence—giving engineering teams the context and proof needed to make trusted release decisions.

Interactive walkthrough

Flow preview

Step 1

Capture context

Every workflow starts from the same project context.

Step 2

Run targeted checks

Change-aware validation executes only what matters for this release risk profile.

Step 3

Decide with evidence

Release Intelligence Layer unifies proof into one release-confidence signal leadership can trust.

Start Free Book Demo

Built for release confidence

Change-aware from commit to CI

One system across IDE, chat, and pipeline

Less blind regression, more signal

release-workflow.json

PR #284 · checkout + pricing update

WARN

Changed

✓Checkout API
✓Cart Service
✓Pricing Logic

Affected

✓Checkout flow
✓Coupons
✓Order confirmation

Verification Selected

✓Checkout flow
✓Pricing validation
✓API contract check

Result

WARN

Coupon edge case failed during pricing validation.

Evidence

2 passed · 1 failed

Contract check clean. Checkout flow passed. Pricing edge case requires review.

Recommendation

Run pricing validation before release

Hold the release until coupon logic is verified and the warning is cleared.

Change → impact → verification → evidence → release decision

Impact planning shows affected tests instantly. Execution runs when write mode is enabled in your IDE, MCP agent, or CI — same project, same evidence.

Code

Starts with source understanding

Impact

Maps change to affected behavior

Run

Executes only what matters

Signal

Returns release-ready guidance

How TestNeo Works

From code change to release decision

Every entry point runs on the same platform, so the workflow stays consistent across your team.

Code Change

Starts from the exact files and components changed in this release.

Impact Analysis

Maps what changed to affected flows, APIs, and risk surfaces.

Verification Generation

Builds meaningful validation for what matters in this release.

Targeted Validation

Runs must-run verification first, then recommended validation based on risk.

Evidence Collection

Unifies outcomes into traceable proof teams and leadership can review.

Release Decision

Converts evidence into clear release guidance teams can trust.

Final release outcome

PASS · Ready to ship WARN · Needs review BLOCK · High-risk issues detected

Why TestNeo Exists

AI writes code. Engineering teams still need answers.

AI can generate code, tests, pull requests, and documentation. Teams still need to know what changed, what should be verified, release risk, and whether it is safe to ship.

Teams still ask

What changed?
What should be verified?
What is the release risk?
Can we safely ship?

What TestNeo does

TestNeo answers those questions automatically by combining code, requirements, designs, APIs, user behavior, and execution evidence.

The output isn’t another test artifact. It’s trusted release readiness.

How you connect

One platform. Every workflow.

Every entry point shares the same project context, release intelligence, and execution history. Pick the one that fits your workflow — or use all of them.

Editor

VS Code Extension

Right-click any function → generate verification. Detect code-change impact and run PR validation without leaving your editor. Works in VS Code, Cursor, Windsurf, and Kiro.

Learn more →

In your repo

Playwright AI SDK

Write plain-English steps inside native Playwright tests. Runs locally, publishes to your team dashboard. No new runtime.

Learn more →

Terminal & CI

TestNeo CLI

Run .testneo files from shell or CI pipelines. Same project, same release signal, no browser required.

Learn more →

AI chat & agents

MCP AI Agent

PR validation, impact analysis, and release briefs — from the same AI thread your team already works in. Claude, Cursor, Copilot — one shared context, one confirm to run.

Learn more →

In your repo

Bring AI-Native Test Automation into Playwright

Write tests in plain English, execute them in native Playwright, and optionally publish results to TestNeo for release visibility and evidence.

Start Free (10 Guest Runs) Read SDK Docs

Works with @playwright/test TypeScript & JavaScript Node 18+ Any CI npm install & go

Step 1

Describe steps in plain English

Use ai.run, ai.step, ai.verify directly in your Playwright tests.

Step 2

Execute locally in Playwright

No black-box runtime. Runs in your local/browser test context.

Step 3

Publish to TestNeo (optional)

Push run history to your project dashboard for team visibility.

import { test, expect } from "@testneo/playwright-ai-sdk";
test("inline hybrid", async ({ page, ai }) => {
  await ai.run(`
    Navigate to https://www.saucedemo.com
    Enter username as "standard_user"
    Enter password as "secret_sauce"
    Click on Login button
    Verify "Products" is visible
  `, {
    autoPublish: {
      projectId: Number(process.env.TESTNEO_PROJECT_ID),
      testName: "inline hybrid quickstart"
    }
  });
  await ai.step("Add Sauce Labs Backpack to cart");
  await expect(page.locator(".shopping_cart_badge")).toHaveText("1");
});

Runs locally, like your tests already do

No black-box runtime. Your tests run on your Playwright context, with your debugger and your traces.

Mix AI steps with native Playwright

Plain-English steps and page.* / expect() live in the same test. Use whichever fits the moment.

Strict, balanced, or adaptive — you pick

Tighten down for CI gates, loosen up for local exploration. Same SDK, three modes for different jobs.

Sync runs to your team dashboard

Optional one-line publish pushes results to TestNeo so the rest of your team gets visibility — no extra plumbing.

TestNeo CLI — Run .testneo files from your terminal or CI. Same signup, project, and API key as the SDK.

npm i -g @testneo/cli · CLI docs → · Overview on this page

Try it now, scale when ready.

10 guest runs without signup, then a 14-day trial for full project history and team workflows.

Get Started Read SDK Docs

In your editor

TestNeo Editor Extension

Generate verification from source code changes without leaving your IDE. Works across VS Code-compatible editors including VS Code, Cursor, Windsurf, Kiro, Gitpod, and GitHub Codespaces.

Install from Marketplace Read Extension Docs

For VS Code Cursor Windsurf Kiro Gitpod Codespaces JavaScript & TypeScript Python, Go, Java free install

Step 1

Right-click any function

Select "Generate Verification with TestNeo" from the context menu.

Step 2

AI maps impact and generates validation

Meaningful checks appear in a side panel in seconds.

Step 3

Run and review inline

Execute verification and see release signal without switching windows.

// Right-click the function below and select "Generate Verification"

export function calculateCheckout(items, taxRate) {
  const subtotal = items.reduce((sum, item) => sum + item.price, 0);
  const tax = subtotal * taxRate;
  return {
    subtotal,
    tax,
    total: subtotal + tax
  };
}

// TestNeo generates validation:
// ✓ Typical checkout with multiple items
// ✓ Zero items edge case
// ✓ Negative tax rate handling
// ✓ Decimal precision verification

Never leave the editor

Full test generation, execution, and results — directly inside your editor with the same TestNeo workflow.

Edit and rerun on the fly

Generated test cases are editable — fix assertions, add steps, tune logic, and re-run instantly.

Sync to your team dashboard

Push results to TestNeo so your team sees what's tested and what passed — one click.

Works with your entire stack

JavaScript, TypeScript, Python, Go, Java — any language you're coding in.

Test as you code.

The TestNeo editor extension is always free to use locally. Sync to the TestNeo dashboard when you're ready to share with your team.

Install Now Read Docs

In AI chat and IDE workflows

Operate verification from the same thread where teams already think.

MCP turns TestNeo into an operational layer for AI-native teams: resolve context, generate validation, execute, watch, and triage without losing the thread. One shared setup. One context model. You still approve writes.

Get Started Free Read MCP Docs See the flow

Your chat connects through MCP to TestNeo, then branches to plain-language steps and a Playwright spec file.

Works with Cursor VS Code Claude Desktop Windsurf Zed + any MCP-compatible client

The flow

Design context to triage—still in one chat.

Click Play to walk through context → triage in one chat.

Context

Waiting…

Generate

Waiting…

Preview

Waiting…

Approve

Waiting…

Execute

Waiting…

Watch

Waiting…

Triage

Waiting…

✓ Same chat thread· Fix suggested· Rerun when you’re ready

From design context to triage—without switching tools.

testneo-mcp · shared team chat

What's our test coverage on the new checkout flow this sprint?

AGENT

74% covered. 3 user stories missing edge-case tests. Want me to draft them from the latest design context?

SDET

Resolve unified context by name for project 47 — name_query "figma checkout", then generate verification with auth_preamble preset saucedemo

AGENT

Resolved "Figma — Checkout flow" → context_id=203. Drafted 4 test cases as NLP + Playwright .spec.ts. Preview before saving?

ENG

Get failure bundle for execution exec_4821 — what broke and what's the fix?

AGENT

Root cause: cart.total selector drifted. suggested_nlp_patch ready: 2-line diff hardens the route. Apply via testneo_update_test_case_nlp?

MGR

Show me pass/fail trend for project 47 this week and top 3 flaky tests.

Built for every role on your team

One chat. Tailored answers based on what you ask.

PM
Product Managers Coverage, regressions, release readiness.
QA
QA Leads Run suites, monitor health, prioritise reruns.
SDET
SDETs Generate, edit, and ship Playwright drafts fast.
ENG
Engineers Triage failures, get root cause + rerun plan in chat.
MGR
Engineering Managers Trends, flakiness, team-level QA posture at a glance.

Connect the TestNeo MCP server in minutes.

Works in any MCP-aware IDE or AI chat. You approve anything that saves, and everyone can see what ran.

Get Started Free Read MCP Docs Browse prompt packs

What every release delivers

From code change to release confidence

TestNeo turns each release cycle into a structured evidence chain — catching regressions, adapting to change, running only what matters, and producing the signal teams need to ship with confidence.

Catch regressions before they ship

Verification generated from real code changes

Start from actual source logic, then generate plain-English verification that reflects real branches, edge cases, and release risk.

Reads function signatures, logic branches, and edge cases
Generates human-readable verification anyone can edit
Supports REST APIs, UI flows, and unit-level logic

CartService.js

function checkout(cart, user) {

// ... 47 lines of business logic

✓ Generated 5 verification cases in 1.2s

1. Navigate to "/cart"

2. Click "Checkout" button

3. Verify "Order confirmed"

Zero flaky maintenance

Validation stays resilient as interfaces shift

When buttons move, IDs change, or layouts shift, verification adapts automatically so teams keep release evidence flowing instead of babysitting selectors.

AI finds elements by context and meaning, not brittle selectors
Logs every adaptation so you know what changed and why
Works across DOM restructures, class renames, and layout shifts

Before — v2.3

✗ #checkout-btn-primary

Element removed in DOM update

Adapted automatically

After — v2.4

✓ Click "Place Order" button

Matched by text content + role

[heal] checkout.testneo:4 selector updated · confidence 97% · test passed

Run only what matters

Impact analysis — know what to verify before you push

Every commit is mapped to affected tests. Know exactly what to run, what's at risk, and what changed — before you push.

Maps code changes to test cases automatically
Prioritises high-risk tests for faster CI feedback
Shows coverage gaps introduced by each PR

feat: update payment flow

3 files changed · 2m ago

High checkout-flow.testneo Must run

High payment-validation.testneo Must run

Med cart-summary.testneo Recommended

Low user-profile.testneo Skipped

4 tests analysed · 2 must run · 1 recommended · 1 skipped

Visual defects caught automatically

Visual regression AI

Catch visual bugs before your users do. Smart AI analyses every pixel, detects flaky tests, and approves changes in bulk. 50× faster than manual review.

95%AI confidence

80%Fewer false positives

50×Faster approvals

10sReview 50 changes

Critical Functional 95% confidence

Payment button moved outside viewport

Recommendation: Reject

Cosmetic Style 91% confidence

Font weight changed 400 → 500 on header

Recommendation: Approve

Classifies: Layout · Content · Style · Functional

⚠️ Flaky pattern detected 80% confidence

5 runs · 2.1% avg diff · 2 flaky regions

Add ignore regions for dynamic content (timestamps, ads)

Reduces false positives by 60–80%

20 comparisons selected

Header redesign v3.0

homepage.pngStyle

pricing.pngStyle

dashboard.pngLayout

✓ Approve all (20)

Baselines updated in 2s

Up to 100 comparisons per batch

Performance regressions surface before deploy

Performance intelligence

Lighthouse scores, Core Web Vitals, and load-time benchmarks baked into every test run. Performance regressions surface before deploy.

Automated Lighthouse audits on every test execution
Tracks LCP, FID, CLS trends across releases
Alerts on regressions before they reach production

LCP

1.8s

FID

45ms

CLS

0.12

↑ 3pts vs last release · CLS needs attention

Full API coverage in every release

API test generation from your specs

Upload a Postman collection or Swagger/OpenAPI spec and TestNeo generates NLP test cases covering happy paths, negative scenarios, auth flows, and boundary values — across every endpoint. When the spec changes, impact analysis flags affected tests automatically.

Postman JSON → NLP test suite with auth and chaining preserved
OpenAPI YAML/JSON → full coverage including edge cases
Schema changes trigger impact analysis on linked tests
Bearer, API Key, and Basic Auth handled automatically

Postman

Swagger

Impact

checkout-api.postman.json ✓ Imported

POST /api/checkout → 4 tests

GET /api/cart/{id} → 3 tests

PUT /api/cart/{id}/items → 5 tests

✓ 12 NLP test cases generated · Auth preserved · Chaining detected

openapi-v3.yaml ✓ Parsed

Endpoints

Tests generated

Auth scenarios

Negative cases

✓ Full coverage · Happy + negative + boundary + auth

Schema change detected

POST /api/checkout — field "coupon" added (required)

High checkout-flow.testneo Needs update

High payment-validation.testneo Needs update

Med cart-total.testneo Review

3 tests affected · 2 must update · 1 review

Release Intelligence Layer

Unified release intelligence across every source of change

Code, requirements, Jira stories, Figma designs, APIs, user behavior, and execution evidence connect into one shared context so teams can understand impact, verify risk, and decide whether to ship.

Data sources

Knowledge
Graph

Requirements

Test cases

Code files

API endpoints

Bugs

Figma screens

When this diagram scrolls into view, a short tour runs by itself.

You can still tap any source or node anytime to explore on your own.

Hotjar → Knowledge Graph

Session recordings reveal real user flows. AI extracts the paths users actually take — including rage clicks and drop-offs.

Checkout flow — 3 rage clicks detected

→ 8 test cases generated

→ 2 bugs linked (payment timeout)

Mixpanel → Knowledge Graph

Funnel analytics show where users drop off. AI generates tests for every step in the funnel — especially the leaky ones.

Payment funnel — 40% drop-off at step 3

→ 12 test cases covering all paths

→ 3 API endpoints at risk

Jira → Knowledge Graph

Requirements and user stories become graph nodes. Every story links to tests, code, and designs automatically.

PROJ-142: Add coupon field

→ 5 test cases · 2 need update

→ CartService.js, PricingAPI

Figma → Knowledge Graph

Design screens map to requirements and visual regression tests. When designs change, affected tests are flagged.

Checkout redesign v3 — 14 screens

→ 14 visual regression tests

→ 3 screens differ from Hotjar flows

Swagger → Knowledge Graph

API specs auto-generate endpoint tests. Schema changes trigger impact analysis across the entire graph.

POST /api/checkout — schema changed

→ 6 tests affected

→ 2 code files need review

Bug reports → Knowledge Graph

Every bug links to the code, tests, and requirements it touches. See the full blast radius of any defect instantly.

BUG-89: Payment timeout on mobile

→ Linked to PROJ-142, /api/checkout

→ 3 tests now cover this path

Requirements node

Click any requirement to see which tests cover it, which code implements it, and which bugs affect it.

24 requirements imported

→ 89% test coverage

→ 3 uncovered (high risk)

Test cases node

Every test traces back to a requirement, code file, and user flow. No orphan tests, no blind spots.

142 active test cases

→ 98% pass rate (last run)

→ 12 generated from user flows

Code files node

See which tests cover each file. When code changes, impact analysis shows exactly what's at risk.

38 files tracked

→ 4 files with no test coverage

→ 2 files linked to open bugs

API endpoints node

Auto-imported from Swagger. Schema changes trigger alerts across connected tests and requirements.

18 endpoints monitored

→ 52 API test cases

→ 1 breaking change detected

Figma screens node

Design screens link to visual regression tests. When Figma updates, baselines refresh automatically.

14 screens synced

→ 14 visual tests active

→ 2 screens updated this week

Coverage based on reality, not guesswork

The Release Intelligence Layer links every source of change and evidence — then drives verification based on real product risk, not disconnected assumptions.

Integrations

Works with your entire stack

One extension, every workflow. TestNeo plugs into where you code, how you deploy, and what you test on.

Code

Map change & generate verification

VS Code

Primary IDE

Live

Cursor

AI-first editor

Live

Windsurf

Agentic IDE

Live

Kiro

AI assistant

Live

Codespaces

Cloud IDE

Live

Gitpod

Cloud dev env

Live

push

Build & test

Automated pipelines

TestNeo CLI

Terminal / CI

Live

GitHub Actions

CI/CD

Live

Jenkins

CI/CD

Live

GitLab CI

CI/CD

Live

CircleCI

CI/CD

Live

Azure DevOps

CI/CD

Live

Jira

Tracking

Live

run

Execute

Cloud & local Chrome

TestNeo Cloud

Managed infrastructure, zero setup

Live

BrowserStack

Real devices via Chrome

Live

LambdaTest

Parallel execution at scale

Live

Local Agent

Run on your machine, behind your VPN

Live

Data stays on your machine

Works behind VPN & firewalls

Real browser on localhost

Windows, macOS, Linux

Pricing

Start free. Scale as you grow.

No credit card required. Install and start generating release-ready verification in minutes.

Free trial

14 days · no credit card

Release assurance

75 release verifications / monthA verification includes generating, executing, and collecting evidence for a release validation workflow.
10 AI queries / day
1 project
Verification generation
VS Code extension
Local & cloud agents

Import limits

5 Figma uploads
2 bug reports
2 PDF documents

Start free trial

Pro

$99/mo

For professional developers

Release assurance

250 release verifications / monthA verification includes generating, executing, and collecting evidence for a release validation workflow.
25 AI queries / day
3 projects
Adaptive execution
Impact analysis
Visual regression AI
API testing (Swagger & Postman)
Release Intelligence Layer

Integrations

CI/CD (GitHub Actions & more)
Jira integration
BrowserStack / LambdaTest

Import limits

20 Figma uploads
5 bug reports
10 PDF documents

Support

Priority support

Get started

Pro+

$249/mo

For power users & teams

Release assurance

1,000 release verifications / monthA verification includes generating, executing, and collecting evidence for a release validation workflow.
50 AI queries / day
10 projects
Everything in Pro
Parallel test execution
Advanced analytics
Performance intelligence

Import limits

100 Figma uploads
50 bug reports
25 PDF documents

Get started

A release verification is one execution run. Test creation, AI queries, and document uploads are tracked separately above. See full usage guide →

AI can generate code. TestNeo helps you trust the release.

Understand what changed. Verify what matters. Know when to ship.

Start Free Book Demo

About us

Building the release confidence layer for modern engineering teams

At the heart of TestNeo.ai is a belief that shipping software should feel more informed, less reactive, and far less fragile. We’re building the operating layer that helps teams understand change impact, verify risk, and make trusted ship decisions.

Powered by NeoSense™ AI Agent and NeoSense™ AI-Q, TestNeo connects code, requirements, designs, APIs, user behavior, and execution evidence into one Release Intelligence Layer — so teams can focus on building great software with real release confidence.

Our mission

Make release decisions so intelligent, evidence-based, and trustworthy that engineering teams can move faster without guessing. Understand change. Verify risk. Ship with confidence.

70%

Less maintenance

2 min

Setup time

IDE platforms

Chrome

Browser engine

Professional Services

AI QA transformation — built, governed, and release-ready

From Playwright automation to AI-powered release operations, TestNeo helps engineering teams operationalize modern QA at scale.

Your repo first Platform optional Evidence-first delivery

Operator playbooks

Triage → Gates → Evidence

Built on the same operator model trusted across the TestNeo ecosystem.

Hands-on delivery across — capability areas we work in

Scoped programs for these areas are in Typical engagements below — hover there for when to engage and what you get.

The gap

AI can generate code and verification.

stable CIclear ownershiprelease decisionstrusted evidencerepeatable workflows

TestNeo services

We don’t just automate tests. We help teams build trusted release systems.

Whether you’re modernizing Playwright, scaling AI-generated testing, or improving release confidence, we operationalize QA on real engineering systems — not pile more specs into CI.

Why teams hire TestNeo

Operator model

Triage, gates, failure intelligence, pass / warn / block — a release system, not AI chaos in CI.

Evidence leadership trusts

Artifacts, readiness reports, risk signals, and audit-friendly evidence — not screenshots, dashboards, or chat logs.

Your stack. your workflow.

Playwright, your CI/CD, your environments, your engineering process. No forced migration, no lock-in, no demo-only automation.

Operational handoff

Documentation, ownership models, release procedures, and team enablement — so your team can operate confidently after delivery.

Transformation programs

Three proven entry points. Combine them for larger transformations. Hover or tap for when to engage and deliverables.

Specialized engagements

Focused programs for critical quality bottlenecks and operating-model gaps.

Flaky-suite stabilization

Reduce noise, stabilize CI, improve reliability, and establish repeatable triage workflows.

Custom release intelligence

Risk models, quality scorecards, executive reporting, and product-specific release metrics.

Agentic QA systems

Cursor, Claude, MCP, and AI workflow integration with governance and operational controls.

QA command centers

Centralized release visibility, failure intelligence, risk scoring, and operational decision-making.

The TestNeo approach

AI can generate code and verification.

Reliable releases require governance, evidence, operational playbooks, and human judgment.

That’s the layer we help teams build.

Start a conversation

FAQ

Common questions, clear answers

Can you build automation for us if we don’t buy TestNeo?

Yes. Professional services run in your repo and CI — the platform is optional. We use the same operator playbooks as the Academy bootcamp and cookbook, with documentation and handoff so your team can run releases after delivery.

Isn’t AI / vibe coding enough?

AI tools generate outputs quickly; they rarely deliver stable CI, clear ownership, release gates, and evidence leadership trusts. We implement that operating layer — governance, playbooks, and human judgment — not another pile of specs in CI.

What is TestNeo.ai?

TestNeo.ai is an AI-Native Release Assurance Platform. It helps engineering teams understand change impact, generate and run the right verification, collect release evidence, and make trusted ship decisions across IDE, CLI, Playwright, and MCP workflows.

Do I need coding skills?

No. TestNeo is designed for all users, from non-technical testers to automation engineers. Use natural language to create tests, or leverage the VS Code extension for code-first workflows.

What is NeoSense™ AI-Q?

NeoSense™ AI-Q is our AI Quality Intelligence layer. It's a context-aware assistant that lets you interact with your test data using natural language. Ask questions about test execution, get intelligent answers, and receive recommendations based on your test history.

Does it integrate with CI/CD?

Yes. TestNeo integrates with Jenkins, GitHub Actions, GitLab CI, CircleCI, Azure DevOps, and more so teams can run targeted verification, collect evidence, and enforce release gates in CI/CD.

What is adaptive execution?

Adaptive execution is TestNeo’s ability to adjust when UI or API details shift, while preserving the intent of the verification flow and recording what changed as part of the release evidence.

Can I migrate existing tests?

Yes. TestNeo can automatically convert existing automation scripts from Selenium, Cypress, and Playwright into natural language tests, making migration seamless with zero rewrite required.

Is my data secure?

TestNeo prioritises security with enterprise-grade encryption, role-based access control, and compliance with industry standards. Your test data and code remain secure. The Local Agent option keeps all data on your machine.

Who can use TestNeo.ai?

Engineering teams across roles — developers, QA leads, SDETs, product managers, and engineering managers — use TestNeo when they need clearer release readiness, better evidence, and safer ship decisions.

How do I get started?

Install the VS Code extension or sign up for the web platform. Start with our free tier — no credit card required. You'll be running tests in under 2 minutes.

Do I need to replace Playwright?

No. You extend it.

Does it run locally?

Yes, by default.

Can I use only Playwright for some steps?

Yes, fully hybrid.

Can I try without signup?

Yes, 10 guest runs.

When do I need API key/project?

For dashboard publish and team usage.

Get in touch

Let's talk about your testing needs

Full name *

Work email *

Company *

Current testing tool *

Inquiry type *

What are you trying to solve? *

Or reach out directly

support@testneo.ai Schedule a call