Question 1

What is Testver, in one sentence?

Accepted Answer

Testver is a self-hosted, AI-native control plane for every major test framework — recording, code generation, test management, dashboards, and a polished Git workflow, all in one tool.

Question 2

How do I install Testver?

Accepted Answer

Set up Testver on a developer laptop, internal server, or VM in minutes. Point it at a folder containing your existing test code and the UI lights up — no database to provision, no agents to deploy across your team, no cloud account to create.

Full installation steps live in the documentation at https://www.docs.testver.com/.

Question 3

Do I have to rewrite my existing tests?

Accepted Answer

No. Testver wraps your existing project rather than replacing it. Tests stay in the same files, run on the same framework runner, and live in the same repo — whether that's Playwright, Cypress, Selenium, WebdriverIO, Cucumber, REST Assured, PyTest, Puppeteer, or Robot Framework. Testver adds a UI, AI assistance, and lifecycle tooling on top.

Question 4

What does Testver detect about my project automatically?

Accepted Answer

Framework type, test file conventions, page-object patterns, fixture locations, environment-variable usage, locator strategies, and existing tags / metadata. This drives style-aware code generation so AI-written tests look like the rest of your codebase.

Question 5

Which test frameworks are supported?

Accepted Answer

Ten frameworks are first-class: Playwright, Selenium, Appium, Cypress, WebdriverIO, Cucumber, REST Assured, PyTest, Puppeteer, and Robot Framework. Each has a dedicated adapter that translates Testver actions into native framework calls — recording, code generation, and runtime instrumentation all use the framework's own primitives, not a shim.

Beyond these, Testver also discovers and reports results from Jest, Vitest, Mocha, TestNG, JUnit, and the .NET runners (NUnit, xUnit, MSTest). Framework support is pluggable; additional adapters can be added without changing the core platform.

Question 6

Which programming languages can the AI generate tests in?

Accepted Answer

TypeScript and JavaScript are primary across the JS-based runners (Playwright, Cypress, WebdriverIO, Puppeteer, Cucumber-JS, Jest, Mocha). Python covers PyTest and Robot Framework. Java covers REST Assured, Selenium, and JUnit / TestNG. C# / .NET covers Selenium and the .NET runners (NUnit, xUnit, MSTest).

The generator follows your project's existing conventions — naming, file layout, helper patterns — rather than imposing a fixed style.

Question 7

Does Testver support BDD / Cucumber?

Accepted Answer

Yes. Cucumber is one of the ten first-class frameworks. Feature files are recognized and editable through the same UI; the AI can generate step definitions from feature scenarios, and recordings can be exported as Cucumber steps when the project is configured that way. Scenario Outlines are rolled up so every Examples row shows as its own result variant.

Question 8

Can different projects in the same Testver instance use different frameworks?

Accepted Answer

Yes. Framework choice is per-project. One Testver instance can host a Playwright project, a PyTest project, and a Robot Framework project side-by-side — or any other mix of the supported frameworks. The AI assistant, dashboards, scheduler, and reporting all work uniformly across them.

Question 9

What about mobile testing?

Accepted Answer

Native mobile is fully supported. Switch a project to Mobile mode and you can record, AI-generate, and run native Android and iOS tests with Appium — on real cloud devices or on phones connected to your own machine — with self-healing locators and the same dashboards, scheduling, and reporting you get for web. Mobile-web testing via Playwright emulation is supported too.

Question 10

How does Testver's cloud AI work?

Accepted Answer

Testver is the one cloud AI provider built into the tool. Create an account at testver.com, activate a plan (the free Starter takes two minutes, no card required), and connect the tool from Settings → LLM → Testver. That single connection powers every AI feature out of the box — assistant, recorder, test generation, failure analysis — with frontier models managed and optimized by Testver.

No provider accounts, no API keys to manage, no model configuration. You prepay for AI credits and the platform handles the rest.

Question 11

Do I have to use Testver's cloud AI, or can I run my own model?

Accepted Answer

Your choice — there is no lock-in, even on the AI. Testver's managed cloud AI is the zero-setup path to frontier models, or you can run a local model on your own hardware instead.

For local models, both Ollama and LM Studio are supported. With a local LLM, the entire AI surface is completely free.

Question 12

Can I run Testver fully offline?

Accepted Answer

Yes — point the LLM router at a local Ollama or LM Studio instance (Llama 3, Qwen, Mistral, DeepSeek, etc.) and the entire AI surface works without an internet connection. Recording, code generation, and chat all run against the local model.

Some features that depend on frontier-class quality (large-context refactors, very long failure analysis) read better with the managed cloud models — but nothing is gated.

Question 13

What data is sent to the AI, and what does Testver store?

Accepted Answer

Only what the current task needs: the prompt, the relevant code or test artifacts, and the conversation history for that session. There is no telemetry channel — Testver does not phone home with usage data.

With Testver's cloud AI, your prompts flow from your installation to the AI gateway that serves your requests; the account platform records only usage totals (credits spent), never your prompts or test data. If you need everything to stay on your own infrastructure, run a local model via Ollama or LM Studio.

Question 14

Can different projects use different AI setups?

Accepted Answer

Yes. The AI setup — Testver cloud AI or a local model, plus temperature and tool-execution policy — can be configured per-project. One project might use Testver's managed cloud AI for frontier-quality generation while another runs Llama via Ollama for fast, free log summarization — all on the same Testver instance.

Question 15

What can the AI assistant actually do — and is it safe?

Accepted Answer

The assistant has a curated tool palette: file reads, file writes, browser automation actions, test execution, and git operations. Every tool call goes through a permission gate by default — the user explicitly approves (or denies, or "always allow") each tool the assistant tries to invoke.

Permissions are per-user, per-tab, and audited. Nothing happens to your repo or your test runs without an explicit grant.

Question 16

What are AI credits, and what consumes them?

Accepted Answer

AI credits are the prepaid currency for Testver's managed cloud AI. Every AI action — assistant conversations, recorder code generation, test-case generation, failure analysis — consumes credits in proportion to the AI work involved (the model used, prompt size, and output length). Everything else in Testver is free and consumes nothing.

Your dashboard shows credits used, credits remaining, and a daily usage chart, so there are never surprises.

Question 17

How do plans work? Do they auto-renew?

Accepted Answer

Plans are one-time prepaid purchases for a fixed term — nothing ever auto-renews and no card is kept on charge. Each plan grants a monthly allowance of AI credits.

When a term is ending you can renew ahead: buying while your plan is active books your next term, which starts the moment the current one ends. If you let a plan lapse, your tool and tests keep working — only the managed AI pauses until you buy again.

Question 18

Do unused credits roll over to the next month?

Accepted Answer

Monthly cycle credits don't roll over — each cycle starts fresh with your plan's full allowance.

Extra usage packs are different: they fill a separate reserve that never expires. The reserve is only consumed after your cycle allowance runs out, so packs you buy are never wasted.

Question 19

What happens when my credits run out mid-cycle?

Accepted Answer

AI features pause — a hard stop, never an overage bill. Your tool, tests, and all non-AI features keep working normally.

To keep going you can top up instantly with an Extra usage pack, or wait for your next cycle or renewal. On a team plan, ask your team admin to raise your allocation.

Question 20

Is there a free plan?

Accepted Answer

Yes — the free Starter plan is a one-time activation: it grants AI credits to try every AI feature, valid for 30 days, no card required. It's available once per person, the credits don't refresh, and you can upgrade to a paid plan at any time.

And remember: with a local LLM (Ollama or LM Studio), AI is free forever — no plan needed at all.

Question 21

How do payments work? Which currencies are supported?

Accepted Answer

Payments are processed securely by Razorpay — cards, UPI, and netbanking, with international cards supported. Prices display in INR for customers in India and USD everywhere else, detected automatically.

Every purchase gets an emailed receipt with an invoice number, and your payment history is always available on the billing page. Testver never sees or stores your card details.

Question 22

How do team plans work?

Accepted Answer

Team plans are per-seat with a shared monthly credit pool. The team owner buys seats, invites members by email, and allocates each member a monthly credit share from the pool — allocations repeat automatically every cycle and can be adjusted any time.

The owner sees each member's usage at a glance, gets notified when a member runs out, and can top up the whole pool with extra usage packs. Members never need to handle billing at all.

Question 23

Do you offer custom or enterprise plans?

Accepted Answer

Yes. For larger teams we build custom plans around your workflow — credit volumes and team pools sized to your organisation, invoice and bank-transfer billing, priority onboarding, and dedicated support. Custom plans stay off the public pricing page and are set up for your account by our team.

Tell us a little about your team at https://testver.com/contact/sales and we'll get back to you within one business day.

Question 24

What is your refund policy?

Accepted Answer

Because plans are prepaid, short-term, and never auto-renew, purchases are generally final. If something went wrong — a duplicate charge or a payment captured without credits arriving — contact support@testver.com and we'll make it right.

The full details are in our Terms of Service at https://testver.com/legal/terms.

Question 25

Where does my data live?

Accepted Answer

Wherever you install Testver. Project metadata, run history, recordings, and reports are stored locally in SQLite databases under a configurable data directory. There is no required cloud service.

For multi-user deployments, point the data directory at shared storage (NFS, EFS, etc.) and front Testver with a load balancer.

Question 26

Does Testver send anything to the cloud by default?

Accepted Answer

No. Out of the box, the only network traffic is between the browser, the Testver server, and the LLM provider you configured. There is no telemetry endpoint, no analytics SDK, and no automatic update check.

Question 27

How does authentication work?

Accepted Answer

Local username/password with bcrypt + JWT sessions out of the box. SSO via OIDC and SAML is available for enterprise deployments — sessions are recorded so admins can revoke any active token. Pre-shared API tokens cover machine-to-machine integrations.

Question 28

Is there role-based access control?

Accepted Answer

Yes — admin, developer, and viewer roles ship by default, with per-resource permissions (projects, runs, reports, connectors). Role assignments are audited, as are sensitive actions (credential changes, RBAC edits, project deletion).

Question 29

Is there an audit log?

Accepted Answer

Yes. Every authentication event, every connector touch, every git mutation, every credential prompt resolution, and every privileged settings change is logged with timestamp, user, IP, and action context. The log is queryable from the admin UI and exportable as CSV / JSON.

Question 30

How do I run tests automatically — is there CI integration?

Accepted Answer

The built-in scheduler is the primary path today. Schedule any test, suite, or report on a cron — daily smoke, weekly regression, monthly reporting — and Testver handles dispatch, retries, notifications, and report distribution without an external orchestrator.

Webhook-triggered runs from external CI systems are on the roadmap; they aren't available today.

Question 31

Can Testver push defects to Jira?

Accepted Answer

Yes. The Jira connector is bidirectional — a failed test can auto-create a defect, link it to the run, and update its status when the test passes again. Defects opened externally can be linked to test cases for traceability.

Other defect trackers can be wired up via custom connector configuration; Jira is the only one that ships out of the box.

Question 32

Does it integrate with Slack?

Accepted Answer

Yes — as outbound notification destinations. Run summaries, scheduled reports, and on-failure alerts can be dispatched to a Slack channel or via email. Configure once and the destination shows up everywhere a notification rule applies.

Question 33

Which cloud test-runners are supported?

Accepted Answer

Testver works with BrowserStack, Sauce Labs, and LambdaTest. Configure credentials once, then dispatch any test or suite to run on real browsers and devices in the cloud — artifacts (video, traces, screenshots) flow back into the Testver report alongside locally-run tests.

Question 34

Can I trigger Testver runs from a webhook?

Accepted Answer

Not yet — webhook-triggered runs are on the roadmap but not available today. For now, use the built-in scheduler for cron-driven runs and the "Run now" override in the UI for ad-hoc dispatches.

Question 35

Is Testver free?

Accepted Answer

Testver is free to self-host — no test-run limits, no project limits, and no feature gating between editions. Run a local model via Ollama or LM Studio and you get the full product, including every AI feature, at no cost.

For managed frontier AI, buy a prepaid Testver AI credit plan on the Pricing page: one connection powers every AI feature out of the box, with no provider account or API keys needed. Credits pay only for AI usage — they never unlock or gate product features.

Question 36

How do I get support?

Accepted Answer

Visit the support portal at https://support.testver.com/ to open a ticket, browse known issues, or talk to the team.

Question 37

Where is the documentation?

Accepted Answer

The full documentation lives at https://docs.testver.com/ — installation guides, configuration reference, framework adapters, API docs, and walkthroughs for the AI assistant, recorder, dashboards, and connectors.

Answers to the questions we hear most

Getting started

Frameworks & languages

AI & LLMs

Pricing, payments & AI credits

Self-hosting & security

Integrations & ecosystem

Licensing & support

We're here to make adoption painless

Documentation

Support

Community Q&A

Keep your framework. Add AI and a premium toolset.