Testver for Cypress
Write Cypress specs by describing them — and let AI keep them green.
Cypress is pleasant to write and unpleasant to maintain at scale: the specs multiply, the selectors drift, and triage across a large suite becomes its own job.
Testver keeps your Cypress project exactly as it is — same config, same commands, same custom commands — and adds AI authoring, failure analysis and locator healing around it.
Languages supported for Cypress: TypeScript · JavaScript
What a Cypress suite costs to keep
- Selector churn—Chained selectors are quick to write and quick to break when the markup shifts.
- Triage across a big suite—When twenty specs fail from one UI change, finding the single root cause is manual work.
- Reporting is a plugin problem—Run history, trends and team-wide visibility are assembled from third-party pieces.
The same suite, maintained for you
Recorded flows become real specs
Click through the journey once; the recorder writes a spec using your custom commands and data-testid conventions.
Failures grouped by cause
Twenty red specs from one renamed element are presented as one problem with one proposed fix.
Auto-Heal with a verification step
Proposed selector fixes are re-run against the affected specs before they are kept — and can be undone afterwards.
Reporting built in
Run history, pass-rate trends and drill-down into any failure, without wiring plugins together.
Scheduling and CI gating
Nightly runs and pipeline gates for GitHub Actions, GitLab CI, Jenkins, Azure, Bitbucket and CircleCI.
What lands in your repository
Idiomatic Cypress, written into your existing spec folder. Delete Testver tomorrow and this test still runs — there is no Testver runtime, adapter or import inside your project.
it('applies the promo code', () => {
cy.visit('/cart');
cy.get('[data-testid="promo-input"]').type('SAVE20');
cy.contains('button', 'Apply').click();
cy.get('[data-testid="order-total"]').should('have.text', '$79.20');
});Point Testver at your Cypress 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 serviceCypress questions, answered
- Does Testver replace the Cypress runner?
- No. Specs run through your own Cypress installation and config. Testver adds authoring, triage, healing and reporting around it.
- Will generated specs use my custom commands?
- Yes. The recorder and assistant read your support files first, so generated specs reuse your custom commands and data-testid conventions.
- What happens when one UI change breaks twenty specs?
- They are grouped as a single root cause with one proposed fix, which is verified by re-running every affected spec before it is kept.
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.