Write tests in plain English.
Run them in native Playwright.
Ship with confidence.

What makes TestNeo NLP different

Most "NLP testing tools" are keyword-driven frameworks in disguise. They require exact phrasing like Click on button [ID]. TestNeo is different.

• True intent-based NLP — "Click the checkout button" just works
• Self-healing — when your UI changes, tests adapt automatically and log every change
• Playwright-native — runs in your browser, your machine, your CI. No black-box remote execution
• Hybrid — mix plain English and page.* / expect() in the same test
• API coverage — upload Swagger or Postman, get NLP tests instantly. See API testing →
• Release signal — every run feeds your team's release confidence score. See release intelligence →

Not a recorder. Not a keyword tool. Real NLP on real Playwright.

Web automation — plain English in action

Describe flows the way you'd explain them to a teammate. TestNeo finds elements by intent, not brittle IDs.

Navigate to {{base_url}}
Enter username as "standard_user"
Enter password as "secret_sauce"
Click Login button
Verify "Products" is visible
Click "Add to cart" on Sauce Labs Backpack
Verify shopping cart badge shows "1"

API automation — Swagger & Postman to NLP tests

Upload an OpenAPI spec or Postman collection. TestNeo generates NLP test cases covering happy paths, auth, and negative scenarios.

Explore API testing →

Self-healing when UI shifts

When buttons move, IDs change, or layouts shift, verification adapts automatically — and logs what changed so you stay in control.

Playwright hybrid — best of both worlds

Engineers keep full Playwright control. QA writes in plain English. Same test file, same CI.

import { test, expect } from "@testneo/playwright-ai-sdk";

test("checkout hybrid", async ({ page, ai }) => {
  await ai.run(`Navigate to /checkout\nClick "Place Order"`);
  await expect(page.locator(".order-confirmed")).toBeVisible();
});

Playwright AI SDK →