Web application testing, automated with AI
Author, run and maintain browser tests in the framework you already use — locally or across a cloud grid.
Web suites rarely fail because the framework is weak. They fail because writing each spec takes an afternoon, a redesign breaks forty locators at once, and the person who understands the flakiness left last quarter.
Testver takes on that side of the job. It reads your existing project, writes tests in your conventions, runs them wherever you run them today, and repairs them when the UI moves — without replacing your runner or taking custody of your code.
How web testing actually runs here
From an untouched project to a gate on your pipeline, without swapping out the tools your team already knows.
- 1
Point it at your project
Testver detects the framework, language and structure on its own. No migration, no config file, no change to how you already run tests.
- 2
Record a journey, or just describe one
Click through the flow and the AI Record Agent writes an idiomatic spec with stable locators. Or ask the assistant in plain English and it writes against your page objects and helpers.
- 3
Run locally or on a grid
Execute against your own browsers, or on BrowserStack, LambdaTest and Sauce Labs. Results are collected the same way either way, so cross-browser costs you no extra wiring.
- 4
See exactly what the browser did
Every run keeps its trace, DOM, screenshots and video, with run history and pass-rate trends across the whole suite rather than one terminal at a time.
- 5
Let broken locators repair themselves
When a test id is renamed, Auto-Heal reads the page evidence from the failing run, proposes the corrected locator, and re-runs every affected test before the change is kept.
What that buys you
Minutes
Not an afternoon per test
Recording or describing a flow produces working code immediately, so coverage grows at the speed you can review it rather than type it.
Every browser
Without extra plumbing
Local browsers and three cloud grids share one execution path, one report format and one history.
Zero
Migration required
Tests stay plain code in your repo, in your framework. Uninstall Testver tomorrow and the suite still runs.
Describe the journey; get a spec in your own framework
The 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 have to rewrite.
- Written into your repo as plain framework code, with no Testver imports
- Follows the conventions already in the project, including page objects
- 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 }) => {
await page.goto('/cart');
await page.getByTestId('promo-input').fill('SAVE20');
await page.getByRole('button', { name: 'Apply' }).click();
await expect(page.getByTestId('order-total')).toHaveText('$79.20');
});What you get for web testing
AI Record with self-healing locators
Tap-through capture that writes code in your project’s style, not a proprietary format.
Plain-English authoring and refactoring
Full repository context, so new tests fit the suite instead of reading like samples.
Auto-Heal with verification
Fixes are proven by a re-run before they are kept, and can be undone afterwards.
Cloud grid execution
BrowserStack, LambdaTest and Sauce Labs, with results collected centrally.
Scheduling and CI gating
Nightly runs and pipeline gates for GitHub Actions, GitLab, Jenkins, Azure, Bitbucket and CircleCI.
Reporting a manager can read
Run history, pass-rate trends, flakiness and failure drill-down.
Already using a framework?
Testver wraps it rather than replacing it. Pick yours to see exactly how it fits.
PlaywrightAlso works with Puppeteer · Cucumber · Robot Framework
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 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 serviceWeb testing questions, answered
- Do we have to rewrite our existing web tests?
- No. Testver works on the suite you already have — it writes new specs into your project in the same style and runs everything through your existing runner and config.
- Can it run tests across different browsers?
- Yes, on your local browsers 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 DOM from the failing run, proposes the corrected locator and re-runs every affected test before keeping the change — so one UI change stops meaning a day of manual repair.
Keep 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.