Change-aware verification for every release

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

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

TestNeo connects your code, requirements, Figma designs, Jira stories, user behavior, and APIs into a unified Release Intelligence Layer. From change impact to release decisions, teams can verify, investigate, and act directly from their IDE, terminal, CI/CD pipelines, or AI agents.

Flow preview
Step 1

Capture context

Editor Extension / SDK / CLI / MCP 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.

Built for release confidence
Change-aware from commit to CI
One system across IDE, chat, and pipeline
Less blind regression, more signal
release-signal.txt
// PR #284 · pricing and checkout change detected
1. Changed files CartService.js · CheckoutSummary.tsx · PricingAPI.ts
2. Impacted flows Cart → Checkout → Confirmation
3. Selected checks 2 must-run · 3 recommended
4. Generated coverage coupon edge-case validation added
5. Release signal warn until pricing edge case passes
Impact-aware verification · targeted execution · clear release guidance
Code
Starts with source understanding
Impact
Maps change to affected behavior
Run
Executes only what matters
Signal
Returns release-ready guidance

From code change to release decision

01

Code Change

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

02

Impact Analysis

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

03

Verification Generation

Builds meaningful validation for what matters in this release.

04

Targeted Execution

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

05

Release Evidence

Unifies outcomes into traceable proof teams and leadership can review.

06

Decision Signal

Converts validation outcomes into clear release guidance.

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

From code to tested in 30 seconds

Bring AI-Native Test Automation into Playwright

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

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

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

TestNeo CLI

Use the CLI when verification needs to run in the shell, CI, or release automation. Same projects, same intelligence layer, same release signal.

Read CLI docs Get started free

Working example (Sauce Demo) — same flow as the CLI docs:

login.testneo terminal
Natural-language test file
# Test: Sauce Demo login smoke
# Project: 47
# Environment: dev

Navigate to {{base_url}}
Enter username as "standard_user"
Enter password as "secret_sauce"
Click on Login button
Verify "Products" is visible
Install, configure, run
$ npm install -g @testneo/cli

$ testneo config set apiKey tn_your_key
$ testneo config set projectId 47
$ testneo config set defaultEnvironment dev
$ testneo doctor
# ✓ API reachable · projects listed

$ testneo run login.testneo --wait --fail-on-error
✓ result: PASSED · step list in terminal · open run: dashboard URL

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.

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

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
PM
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 47name_query "figma checkout", then generate tests 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

From source code understanding to release confidence

This is how TestNeo stays fundamentally different: it connects code understanding, impact analysis, validation generation, execution, and release guidance into one workflow instead of giving you another pile of scripts.

AI-powered

NLP test generation

Right-click any function and get plain-English test cases generated from your actual code logic. No frameworks to learn, no test code to write.

  • Reads function signatures, logic branches, and edge cases
  • Generates human-readable steps anyone can edit
  • Supports REST APIs, UI flows, and unit logic
CartService.js
function checkout(cart, user) {
  // ... 47 lines of business logic
Go to Definition
Find All References
TestNeo: Generate Tests
TestNeo: Run Tests
✓ Generated 5 test cases in 1.2s
1. Navigate to "/cart"
2. Click "Checkout" button
3. Verify "Order confirmed"
Zero maintenance

Self-healing tests

When buttons move, IDs change, or layouts shift, tests adapt automatically. No more broken selectors or midnight maintenance runs.

  • AI finds elements by context and meaning, not brittle selectors
  • Logs every heal 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
Self-healed
After — v2.4
Click "Place Order" button
Matched by text content + role
[heal] checkout.testneo:4 selector updated · confidence 97% · test passed
Smart selection

Impact analysis

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
AI confidence 95%

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
Built-in Lighthouse

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
92 Performance
LCP
1.8s
FID
45ms
CLS
0.12
↑ 3pts vs last release · CLS needs attention
Swagger & Postman

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
18
Endpoints
52
Tests generated
6
Auth scenarios
14
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

From code to confidence in minutes

See how TestNeo's intelligent platform guides you through the complete testing lifecycle.

Step 1

Start where you code

TestNeo lives right inside VS Code. Right-click any function, select "Generate Tests", and watch AI create comprehensive test scenarios in seconds.

  • Native IDE integration — no workflow disruption
  • AI analyzes your code context automatically
  • Generate tests for functions, components, or entire files
VS Code Integration
Step 2

Execute with one click

Run your tests instantly and see real-time results. TestNeo executes tests on Chrome, captures screenshots, and provides detailed execution logs.

  • One-click execution with real-time status
  • Detailed logs and screenshot capture
  • Automatic screenshot capture for visual validation
Test Execution
Step 3

Understand what matters

Get actionable insights from your test runs. Analytics reveal patterns, identify flaky tests, and show you exactly where to focus for maximum impact.

  • Smart analytics reveal test patterns and trends
  • Identify flaky tests and optimization opportunities
  • Track coverage and quality metrics over time
Test Analytics
Step 4

Ship with confidence

Know the health of every branch before merging. Release quality dashboard gives you complete visibility into test coverage, pass rates, and risk.

  • Real-time branch health and quality metrics
  • Risk assessment before every merge
  • Complete traceability from code to tests
Branch Health Dashboard

Your users already told you what to test

Session replays, funnels, and analytics capture real user behaviour every day. TestNeo turns that data into test cases that cover what actually matters.

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 AI builds a unified context across every source — then generates tests based on real user flows, not guesses from a sprint planning meeting six months ago.

Already on Playwright, Selenium, or Cypress?

Before — Selenium WebDriver
login_test.py
# 47 lines of brittle selectors
driver = webdriver.Chrome()
driver.get("https://app.example.com")
driver.find_element(By.ID, "email")
  .send_keys("user@test.com")
driver.find_element(By.ID, "pass")
  .send_keys("secret123")
driver.find_element(By.CSS_SELECTOR,
  "button.btn-primary").click()
After — TestNeo NLP
login-flow.testneo
// 5 lines. Self-healing.
1. Navigate to "https://app.example.com"
2. Enter "user@test.com" in Email
3. Enter "secret123" in Password
4. Click "Sign In" button
5. Verify "Dashboard" is visible
✓ Passed · 0.9s · Self-healing active
Migrate free — zero rewrite required

Works with your entire stack

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

Watching pipeline...
VS Code
Generate tests...
GitHub Actions
Waiting...
TestNeo Cloud
Waiting...
Results
Waiting...
✓ 12 passed· 0 failed· 1.8s total
Self-healing: 1 element healed · Coverage: 94% · No regressions
Code
Write & generate tests
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

Enterprise outcomes, not just features

✓ Faster verification
✓ Less blind regression
✓ Fewer release surprises
✓ Clear ownership
✓ Trusted release decisions
✓ Evidence leadership can review

One set of playbooks. Three ways to apply them.

1. Learn the playbooks

TestNeo Academy

2. Implement the playbooks

Professional Services

3. Scale the playbooks

TestNeo Platform

AI can generate code. Reliable releases require impact analysis, verification, evidence, and judgment. That’s the layer TestNeo provides.

Start free. Scale as you grow.

No credit card required. Install and start testing in 2 minutes.

Free trial

$0

14 days · no credit card

  • 75 test runs / month
  • 10 AI queries / day
  • 1 project
  • NLP test generation
  • VS Code extension
  • Local & cloud agents
  • 5 Figma uploads
  • 2 bug reports
  • 2 PDF documents
Start free trial

Pro+

$249/mo

For power users & teams

  • 1,000 test runs / month
  • 50 AI queries / day
  • 10 projects
  • Everything in Pro
  • Parallel test execution
  • Advanced analytics
  • Performance intelligence
  • 100 Figma uploads
  • 50 bug reports
  • 25 PDF documents
Get started

Ship tested code, every time.

Install in two minutes. Generate your first test in ten seconds. No credit card required.

Install VS Code extension Start free trial

AI-powered testing for the next generation of software

At the heart of TestNeo.ai is a belief that technology should simplify complex processes, not complicate them. More than a product, TestNeo is a shift in AI-driven software testing — empowering teams, reducing time and costs, and delivering seamless digital experiences.

We're redefining how businesses approach software testing by making it accessible, intelligent, and automated. Powered by NeoSense™ AI Agent and NeoSense™ AI-Q, our platform eliminates manual test writing, framework setup, and constant maintenance — so teams can focus on building great software.

Our mission

Make testing so intelligent and automated that teams never think about test maintenance again. Ship faster, break less, sleep better.

70%
Less maintenance
2 min
Setup time
8+
IDE platforms
Chrome
Browser engine

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 tests 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-powered test automation platform powered by NeoSense™ AI Agent and NeoSense™ AI-Q. It converts natural language inputs into executable test scripts for both Web and API testing. Key features include self-healing automation, Code Impact Analysis, and intelligent reporting. No coding knowledge required.
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. Run tests automatically on every commit with just a few lines of config.
What is self-healing?
TestNeo's self-healing technology uses AI to automatically adapt to UI and API changes. When elements change, tests update themselves without manual intervention, reducing maintenance by up to 70%.
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?
Anyone looking for faster, smarter test automation — QA engineers, developers, product managers, or business analysts. TestNeo simplifies test creation, execution, and reporting for everyone.
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.

Let's talk about your testing needs

Or reach out directly

support@testneo.ai Schedule a call