Testver for Selenium
Keep the WebDriver suite your team has built. Add AI that maintains it.
Most Selenium suites are years of accumulated work — page objects, helpers, waits, CI wiring. Replacing that with a record-and-playback platform means throwing it away. Testver takes the opposite approach: it works on the suite you have.
Your tests stay in Java, Python, C# or JavaScript, in your build tool, run by your runner. Testver adds the authoring, triage and maintenance layer around them.
Languages supported for Selenium: Java · Python · C# · JavaScript
What a Selenium suite costs to keep
- Brittle locators everywhere—Deep XPath and CSS chains break on the smallest markup change, and the fix has to be found by hand.
- Boilerplate per test—Driver setup, waits, page objects — a large share of every new test is structure rather than intent.
- No opinion about the rest—WebDriver drives a browser. Reporting, scheduling, test management and failure analysis are all yours to assemble.
The same suite, maintained for you
AI that writes in your existing structure
New tests follow your page objects, your naming and your helpers, because the assistant reads the repository before it writes.
Auto-Heal for WebDriver locators
Testver captures what the driver actually saw when the test failed, proposes the corrected selector, and verifies it by re-running before anything is kept.
Zero-touch cloud execution
Run the same suite on BrowserStack, LambdaTest or Sauce Labs — for Java, Python and .NET on BrowserStack, Testver wires the vendor SDK for you.
Failure analysis instead of log reading
Failures are grouped, explained, and turned into a concrete proposed fix rather than a stack trace to decode.
A management layer that was missing
Suites, schedules, run history, trends and CI gating on top of the tests you already own.
What lands in your repository
Plain Selenium in your own page-object style — Testver writes it, your build runs it. Delete Testver tomorrow and this test still runs — there is no Testver runtime, adapter or import inside your project.
@Test
public void checkoutAppliesPromoCode() {
cartPage.open();
cartPage.enterPromoCode("SAVE20");
cartPage.applyPromo();
assertEquals("$79.20", cartPage.orderTotal());
}Point Testver at your Selenium project
It detects the framework, language and structure on its own. No migration, no config file to write, no change to how you run tests.
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 serviceSelenium questions, answered
- Will Testver work with my existing Selenium page objects?
- Yes. The assistant reads your repository first, so new tests call the page objects, helpers and naming conventions your team already maintains.
- Which Selenium languages and runners are supported?
- Java with TestNG or JUnit, Python with PyTest, C# with NUnit, xUnit or MSTest, and JavaScript. Your build tool and runner stay exactly as they are.
- Can it run my Selenium suite on a cloud grid?
- Yes — BrowserStack, LambdaTest and Sauce Labs. For Java, Python and .NET on BrowserStack, Testver wires the vendor SDK for you with no changes to your code.
More in the full FAQ or the documentation.
Running more than one framework?
One Testver instance handles all of them — different projects can use different frameworks, languages and AI models.
Playwright
AppiumSee the full feature set, the comparison with other approaches, or try a live demo repo.
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.