Web tests in your framework, written and repaired with AI
Record a journey or describe it in plain English, run it on your own browsers or any cloud grid, and let Auto-Heal fix the locators a redesign breaks.
- Minutes
- Not an afternoon per testRecording or describing a flow gives you working code straight away.
- Any browser
- One report, wherever it ranYour browsers, Testver Grid, BrowserStack, LambdaTest or Sauce Labs.
- Zero
- MigrationTests stay plain code in your repo. Remove Testver and they still run.
How web testing runs in Testver
- 1
Point it at your project
Testver detects the framework, the language and how your project picks its browser and environment. No migration, no config file.
- 2
Record it, or describe it
AI Record writes the test as you click, with annotations and custom steps. Or the AI Assistant writes it from plain English, reusing your page objects.
- 3
Run it anywhere
Your own browsers, Testver Grid, or BrowserStack, LambdaTest and Sauce Labs — the results land in the same place.
- 4
See what really happened
Screenshots, video and Playwright traces stay with the run, and failure analysis separates real bugs from broken tests.
- 5
Heal it and gate it
Auto-Heal proposes the fixed locator and re-runs every affected test before keeping it. CI templates gate the merge.
Describe the journey; get a spec in your own framework
The AI Assistant reads your repository before it writes, so a request lands as code that matches your fixtures, page objects and naming — not a generic sample you then rewrite.
- Plain framework code in your repo — no Testver imports
- Reuses your page objects, fixtures and naming
- Runs through your existing config and runner, unchanged
“Add a test that applies promo code SAVE20 at checkout and asserts the new total.”
test('checkout applies the promo code', async ({ page }) => {
const cart = new CartPage(page);
await cart.open();
await cart.applyPromo('SAVE20');
await expect(cart.orderTotal).toHaveText('$79.20');
});Everything for web testing
AI Record with annotations
Click through a flow and get idiomatic code with ranked fallback locators — through iframes and shadow DOM too.
Plain-English authoring
The AI Assistant reads your repository first, so new tests reuse your page objects and helpers.
Auto-Heal, verified
Broken locators fixed from the failing run’s evidence, re-run before they are kept, and undoable.
Failure analysis
Each failure sorted — real bug, broken test, environment, timeout — with its likely root cause.
Cloud and grid runs
Testver Grid, BrowserStack, LambdaTest and Sauce Labs, all reported in one place.
Schedules and CI gates
Nightly runs, plus gates for GitHub Actions, GitLab, Jenkins, Azure, Bitbucket and CircleCI.
Already using a framework?
Testver wraps it rather than replacing it.
PlaywrightAlso works with Puppeteer · Cucumber · Robot Framework
Web testing, answered
Do we have to rewrite our existing web tests?
No. Testver works on the suite you already have — new specs are written into your project in the same style and everything runs through your existing runner and config.
Can it run our tests on cloud browsers?
Yes — on Testver Grid with no vendor account, or on BrowserStack, LambdaTest and Sauce Labs. The same suite runs either way and the results land in the same place.
What happens when a redesign breaks our locators?
Auto-Heal reads the evidence from the failing run, proposes the corrected locator and re-runs every affected test before keeping the change. An administrator chooses whether it suggests or applies.
Which web frameworks does it support?
Playwright, Selenium, Cypress, WebdriverIO and Puppeteer, plus Gherkin (Cucumber, Reqnroll, behave, pytest-bdd) and Robot Framework suites — in TypeScript, JavaScript, Python, Java, Kotlin, C# and more.
Start testing web 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.js 22 or newer (24 recommended) 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.