Can I run load tests with the same API suites?
Yes. Export any API NLP suite as a
k6 kit from Test Manager — same flows you already run functionally. Tweak
VUS,
DURATION, and
BASE_URL locally (or in CI), run with Grafana k6 or Docker, then upload
k6-out/testneo-import.json to
Load Insights for p95, error rate, throughput, and pass/warn/fail verdict history. Full walkthrough:
k6 Load Export & Insights docs.
What counts as one PR validation on my plan?
One PR validation = one release review workflow for a pull request or branch diff. TestNeo runs impact analysis on changed files, assigns a risk score (0–100), highlights test gaps, and produces a release brief you can open at /web/pr-validation/<workflow_id>. Triggers: MCP in Cursor/VS Code, the PR Validation page, or GitHub auto-validation. Each new PR (or first validation of that PR) uses one credit; re-opening or updating the same workflow does not. Optional test execution inside a validation uses your separate test runs allowance. Pro includes 200/month; Release Intelligence includes 800/month with full PASS/WARN/BLOCK and GitHub Check Runs.
Can you build automation for us if we don’t buy TestNeo?
Yes.
TestNeo Labs engagements 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 is an AI-Native Engineering & Release Intelligence Platform. It connects requirements, development changes, verification, Engineering Memory, and Release Intelligence — so QA, developers, DevOps, product, and engineering leaders share one evidence-based release confidence signal (PASS / WARN / BLOCK) across IDE, CLI, CI/CD, and MCP workflows.
Is TestNeo an AI testing tool?
No — and it is not a Playwright, Salesforce, or Agentforce replacement either. TestNeo is the intelligence, verification and release layer across tools teams already use. Generation and automation are inputs. The product is the release decision—backed by evidence you can inspect, with PASS / WARN / BLOCK for applications and AI agents.
We already use Claude / Cursor. Why TestNeo?
Coding agents plan and edit. TestNeo executes verification against your systems, retains evidence, matches Engineering Memory, and returns PASS / WARN / BLOCK for releases and agent runs. Bring your agent; bring your release brain (TestNeo).
We use CrewAI or LangGraph. Do we need another agent platform?
Aren’t evals / LLM-as-judge scores enough?
No. Judge scores and datasets measure writing quality. They do not prove a refund, confirmation, or memory isolation happened. TestNeo
Verify is the ship decision for one run (PASS / WARN / BLOCK).
Eval is oracle health across many gates — not an LLM beauty bench. See
problems teams hit today.
Does TestNeo auto-heal failing assertions?
Heal is suggest only. Auto-rewriting assertions can hide real product breaks. A human reviews the evidence and owns PASS / WARN / BLOCK. Generation from chat is optional support for some product paths — not the release decision.
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 encryption, role-based access control, and org-scoped credentials. The Local Agent option keeps browser/API execution on your machine. For AI features, you can use
TestNeo managed AI or
bring your own Groq, Azure OpenAI, or a private OpenAI-compatible gateway (Ollama, vLLM, LiteLLM). Org keys are encrypted at rest. See
AI providers.
Can we use our own Ollama or self-hosted LLM?
Yes. In Settings → AI Providers, choose Private / OpenAI-compatible and set your HTTPS /v1 base URL plus model names (from ollama list or your gateway). From TestNeo SaaS, the endpoint must be reachable over HTTPS (Cloudflare Tunnel, reverse proxy, ALB, or PrivateLink)—not localhost. PR validation, release readiness, and agent verification stay deterministic either way; the model is used where AI authoring and chat need it.
Does a live NLP run send steps to Groq or OpenAI?
No on the happy path. NLP execution is a real browser (Playwright) plus selector memory. A language model is a last resort for unmatched steps or leftover Studio chat — not every click. Evidence (screenshots, logs, oracles) is what the run records.
Do you send our tests to a public LLM?
Not for compile-first surfaces: live run, Predict, PR PASS / WARN / BLOCK, release gates, and agent oracles. Optional generation and Help chat use
TestNeo managed AI or
your org BYOK (Groq, Azure, Ollama-compatible). Semantic matching uses MiniLM embeddings on TestNeo, not your chat provider. See
AI providers.
Can we use TestNeo with no language model at all?
Yes for run and release decisions. Import or write NLP yourself, execute locally or in cloud, and still get impact, memory, and gates. You skip Studio generation and leftover chat. That is compile-first — not an air-gap claim and not “no AI” (embeddings and oracles still exist).
Do we pay less if we bring our own model?
No — seat pricing is the same. You pay TestNeo for the release control plane (Studio, PR risk, gates, memory, seats). You cover your own GPU or cloud LLM costs. We don’t mark up your tokens when you bring your own provider.
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
Chrome Quick Test extension or the VS Code extension, or sign up for the web platform. Start with a 14-day free trial — no credit card required. After the trial, stay on Free or upgrade to Starter ($19), Pro ($79), or Release Intelligence ($149).
Do I need to replace Playwright?
No. You extend it. Generation and Playwright-oriented workflows are part of application verification. The product outcome is release confidence—not script volume.
Does it run locally?
Yes, by default.
Can I use only Playwright for some steps?
Yes, fully hybrid.
Can I try without signup?
Yes. Use the
live playground — starts on Web Automation (NLP), 10 guest runs, no account required.
When do I need API key/project?
For dashboard publish and team usage.
