Your testers and the vikingQA agent build one suite per client. The client sees every test, every result and the video. The tests stay in the client's own code repository.
42 tests in one suite. Each run has a video and the logs.
Each client gets a project, with its own suite, environments and encrypted login details. Invite the client with the Customer role. They see only their project: the test cases, the results and the video, and they can run a test by hand.
A functional tester records a flow in the browser, or describes it in chat. An automation engineer writes a test in the tools they already use, and can review what the agent writes. The agent explores the application, writes the automated test and heals it when the application changes.
The tests are stored in a code repository, in a standard open format (Playwright). You keep running the suite for the client, or you hand the repository over when the engagement ends. In both cases the tests keep working, with or without vikingQA.
They add tests as code. They can review each change the agent writes, or vikingQA can add and heal tests by itself. They choose, per project.
Your testers record a flow or run a test case by hand. The client's key users join with the Customer role and do the same. They never write code.
It defines test cases, explores the application, writes the automation and heals a test when the screen changes. One senior tester is not copied onto every account.
No. Seats are for your own team. People with the Customer role need no seat. They see only the projects you share.
Test cases, results and evidence, and they can run a test by hand. They cannot see your other clients, your settings or your billing.
You or the client. You choose for each project. In both cases the tests are stored in a code repository, in a standard open format (Playwright). A hand-over is a transfer of that repository.
Connect the repository. Those tests become the list. The agent adds to them. Suites written in another tool stay where they are.
They can. Anyone on your team can accept a change in vikingQA, or vikingQA can add and heal tests by itself. You choose per project.
Tests run from a fixed IP address the client can add to an allow-list. Login details are encrypted variables for each environment.
Yes. Run the tests on vikingQA, on their infrastructure, or both.
Apply through the partner program. Project-based terms for partners are on our roadmap.
Start free with your own application. No credit card.
We build vikingQA with a small group of design partners.Join the design partner program