vikingQA catches bugs before your customers do. Keeping a test suite fast, up to date and running on every release is a product in itself. That product is what we built, and the tests stay yours.
Who repairs your tests each time your interface changes?
Self-healing tests: when your application changes and a test is out of date, the agent explores again and heals the test. vikingQA can merge the change by itself, or your team reviews it first.
When a test fails now and then, who decides if it is a real bug or a flaky test?
Tests run as plain Playwright code in isolated browsers, with retries. Each failure comes with video and trace, so the decision takes minutes.
Will you build orchestration, retries, isolation, logging and storage to run tests at scale?
Tests run in isolated browsers in the vikingQA cloud, with orchestration, scheduling and evidence storage included. You can also run them on your own infrastructure. You control how many run in parallel in each batch.
Does your setup remember how your product works, or does it start from zero in every session?
Each session starts from your test suite and your project description. The agent also reads the documents and tickets you connect, in Confluence, Notion, Jira or Linear.
Is your internal setup good enough to put in front of clients and external testers?
A finished product you can give to clients, agencies and acceptance testers, with a role for external users.
Who builds the dashboards and the Slack alerts, and who collects the logs when something breaks?
Video, Playwright trace, network log and console log for every run. The agent files the issue in Jira or Linear and posts to Slack when you ask it. Automatic Slack alerts on a failed batch are on our roadmap.
Who builds sign-in, roles, the audit log and security, and who keeps them running?
Sign-in, roles and project-scoped API tokens are part of the product on day one. Single sign-on, an audit log with export and an uptime commitment are on our roadmap.
Who keeps test generation, CI and reporting connected in your repository?
Plain Playwright in your repository. Run it in the vikingQA cloud or in your own CI. No proprietary runner.
Who follows new models, API changes and browser updates?
We do. Your tests are plain Playwright and keep running when the models change.
An estimate. It counts test maintenance only. The time to follow model, API and browser changes comes on top.
~$8,000/ month
vs. the vikingQA Basic plan at $199/month, with monthly AI credits.
The plan includes a monthly credit allowance. When you reach it, top up in the app. No plan change needed.
It is a good start, and you keep it. Connect the repository and your suite becomes your test list in vikingQA. The agent adds to it, and heals a test when your application changes: it explores again and updates the test.
The tests. Your tests are stored in your own code repository, in a standard open format. If you cancel, every test stays and keeps running. For developers: every test is plain Playwright in your git.
You can, for one run. Then each run needs the model again, so each run is slow and has an AI cost. vikingQA uses the model to write the test once. After that, a run is code execution.
Running your committed Playwright tests costs no AI credits. Credits pay for the agent's work: writing, exploring and healing tests. See pricing
No. vikingQA is a product your team uses. Your developers, your testers and the agent own the suite together. We do not write your tests for you.
Yes. If your in-house tests are Playwright files in GitHub or GitLab, connect the repository and continue from there.
A 30-minute demo, on your product, with your flows.