Testver for Robot Framework
Keyword-driven tests, written and maintained with AI — still plain .robot files.
Robot Framework’s readability is its strength, and its maintenance burden is the flip side: keyword libraries sprawl, locators live in resource files, and consistency depends on everyone remembering the conventions.
Testver reads your existing keywords and resource files and writes new tests that reuse them, rather than inventing a parallel vocabulary.
Languages supported for Robot Framework: Robot Framework · Python
What a Robot Framework suite costs to keep
- Keyword sprawl—The same action ends up implemented three times under three names across resource files.
- Locators scattered across resources—A UI change means hunting through variable files to find every affected selector.
- Reports without diagnosis—Robot produces thorough logs, but deciding why something failed is still a human reading them.
The same suite, maintained for you
New tests reuse your keywords
The assistant reads your resource files first, so generated cases call the keywords you already maintain.
Locator healing in the resource layer
When a selector breaks, the fix is proposed where the locator actually lives — and verified by re-running.
Plain English to keyword-driven case
Describe the scenario; get a properly structured test case in your suite’s style, not a generic template.
Central run history
Every execution collected in one place with trends and drill-down, alongside your other frameworks.
Scheduling and pipeline gates
Run suites on a schedule or gate a deploy on them, without writing the orchestration yourself.
What lands in your repository
Generated case reusing the keywords already in your resource files. Delete Testver tomorrow and this test still runs — there is no Testver runtime, adapter or import inside your project.
*** Test Cases ***
Checkout Applies Promo Code
Open Cart Page
Enter Promo Code SAVE20
Apply Promo
Order Total Should Be $79.20Point Testver at your Robot Framework 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 serviceRobot Framework questions, answered
- Will generated tests reuse my existing keywords?
- Yes. Testver reads your resource files before writing, so new cases call the keywords you already maintain instead of inventing a parallel vocabulary.
- Does it work with SeleniumLibrary and Browser Library?
- Both. Testver follows whichever library your suite already uses, and writes plain .robot files into your existing structure.
- Where are locator fixes applied?
- In the resource layer where the locator actually lives, so one fix covers every case that uses it — verified by a re-run 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.