One application. Your existing test project. AI everywhere.
No platform to migrate to. No agents to deploy. Install Testver, point it at any test framework folder, and you're up.
From install to a running test, in four steps
Testver is a single application that bundles the entire test lifecycle. Install once, point it at any test project, configure your LLM, and you're authoring AI-assisted tests within minutes.
- 01
Install Testver
One command via npm — npm install -g @testver/testver, then testver serve and open http://localhost:3700. Set up in minutes on Windows, macOS, or Linux, entirely on hardware you control — no cloud account to create, no per-seat licenses to negotiate, no agents to deploy across your team.
Available for
macOSWindowsLinuxSelf-hosted on your hardware — no cloud account, no per-seat fees.
- 02
Open your test project
Existing Playwright, Cypress, Selenium, Appium, WebdriverIO, Cucumber, REST Assured, PyTest, Puppeteer, or Robot Framework project — web or native mobile, or a fresh empty folder. Testver auto-detects the framework, language, and your project's conventions.
Project detected
Framework
Playwright
Language
TypeScript
Test files
42
Page objects
12
Conventions auto-detected — generated tests match your existing style.
- 03
Configure your AI
Settings → LLM. Connect Testver cloud AI with a single connect token — frontier models, no API keys, no configuration — or point at a free local model via Ollama or LM Studio. Per-project overrides let different projects use different setups.
Choose your AI
Testver cloud AIOllamaLM StudioCloud: managed frontier models, one connection · Local: completely free
- 04
Author, run, schedule, manage
Record real user journeys with smart selectors. Generate tests with AI in your project's style. Run locally or on cloud grids. Schedule recurring runs. Dispatch reports to email or Slack. All from the same UI — no second tool to license.
AuthorRecorder + AI codegen
RunLocal & cloud grids
ScheduleCron + run-now
ManageTMS, defects, reports
What this looks like in practice
A walkthrough of how a QA engineer might go from setup to a scheduled, AI-generated test in under twenty minutes.
Set up Testver
npm install -g @testver/testver, then testver serve. Two-minute setup — nothing else to provision.
Open your project
Pick your existing test framework folder. Testver auto-detects the framework, language, and conventions.
Configure your AI
Settings → LLM → connect Testver cloud AI with one token, or point at a local Ollama / LM Studio model.
Record a journey
Hit Record, click through the new feature once, stop. Smart selectors and screenshots captured automatically.
Generate the test
AI writes a clean test in your project's style. Inspect, tweak if needed, save.
Run + commit
Test passes. Built-in Git workflow handles the commit and push.
Schedule the daily run
Add the new test to the daily smoke suite. Reports go out by email at 6am.
One platform does it all
No microservice sprawl. No separate orchestration layer. One Testver application powers every part of the product you interact with.
All-in-one platform
One application bundles the UI, orchestrator, browser pool, scheduler, and reporting service. No microservice sprawl, no separate database to provision, no integration glue to maintain.
Framework adapter layer
Per-framework adapters translate Testver actions into native calls — Playwright, Cypress, Selenium, Appium, WebdriverIO, Cucumber, REST Assured, PyTest, Puppeteer, Robot Framework. Recording captures intent; the adapter knows how each framework expresses it — web or native mobile.
Self-hosted, multi-user ready
Run it on a laptop for one developer or on shared infrastructure for the whole QA org — same product, same data layer. RBAC, audit logging, and per-tenant isolation come built in.
Running in three commands
No account required to install, nothing to configure first, and your existing project works as-is.
Install it
One global npm package. Node 18 or newer is the only prerequisite.
npm install -g @testver/testverGo to your test project
Testver runs from inside the framework project you want to test, so change into that folder first.
cd path/to/your-test-projectStart the dashboard
Opens at localhost:3700. Testver detects the framework, language and structure of the project you started it in and lists your tests — no configuration to write.
testver serveTypically under five minutes, start to first generated test.
Full installation guide — prerequisites, ports, running as a serviceKeep your framework. Add AI and a premium toolset.
Set up in minutes. Self-host on your own hardware. Describe a test in plain English and get working code in your own framework — in a fraction of the time.