Show all questions
Can I run load tests with the same API suites?
Yes. Export any API NLP suite as a
k6 kit from Test Manager, using the 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 is one release review workflow for a pull request or branch diff. TestNeo runs impact analysis on changed files, assigns a risk score from 0 to 100, highlights test gaps, and produces a release brief you can open at /web/pr-validation/<workflow_id>. Triggers: MCP in Cursor or VS Code, the PR Validation page, or GitHub auto-validation. Each new PR, or the 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 a month. Release Intelligence includes 800 a 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. The work uses 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. TestNeo Labs implements that operating layer: governance, playbooks, and human judgment.
What is Regression Intelligence?
A suite recommender on
Release Readiness. Connect or upload production analytics, refresh analysis, open a ranked
run pack in Test Runner, and generate drafts from knowledge gaps. You approve what gets created. Guide:
Regression Intelligence docs.
Is TestNeo an AI testing tool?
Yes. It generates tests in natural language, runs UI and API checks, and keeps the evidence. Release readiness is a later step: PASS, WARN, or BLOCK from the checks and rules you configured, for applications and AI agents.
We use CrewAI or LangGraph. Do we need another agent platform?
Aren’t evals / LLM-as-judge scores enough?
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, or BLOCK. Eval is oracle health across many gates.
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, or BLOCK. Generation from chat is optional support for some product paths, not the release decision.
What is NeoSense™ AI-Q?
NeoSense™ AI-Q is the AI Quality Intelligence layer. It is a context-aware assistant for questions about test execution, with answers and recommendations based on your test history.
Does it integrate with CI/CD?
Yes. TestNeo integrates with Jenkins, GitHub Actions, GitLab CI, CircleCI, and Azure DevOps so teams can run targeted verification, collect evidence, and enforce release gates in CI/CD.
What is adaptive execution?
When a selector or response detail shifts, TestNeo can keep the intent of the check and record what changed. It does not rewrite assertions on its own. A person still owns PASS, WARN, or BLOCK.
Can I migrate existing tests?
TestNeo can convert existing Selenium, Cypress, and Playwright scripts into natural language tests. Review the result before you rely on it.
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?
Not 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.
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 the cloud, and still get impact, memory, and gates. You skip Studio generation and leftover chat. That is compile-first. It is not an air-gap claim, and 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. TestNeo does not mark up your tokens when you bring your own provider.
Who can use TestNeo.ai?
Engineering teams across roles, including 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 is required. After the trial, stay on Free or upgrade to Starter ($39), Pro ($99), or Release Intelligence ($149) per user each month.
Can I use only Playwright for some steps?
Yes. Keep Playwright for the steps you already trust and add plain-English checks where scripts are harder to maintain. The Playwright AI SDK is built for that mix.
When do I need an API key and a project?
When you publish runs to the dashboard, share a project with your team, or call TestNeo from CI, MCP, or the CLI. Guest playground runs do not need one.
TestNeo