Give each client project its own test suite. Run it before each delivery, and find what broke before the client does. Show the client the results, and let them take part if you want. The tests stay with the project: you keep running them for the client, or you hand them over.
42 tests in one suite. Each run has a video and the logs.
Invite clients and external testers with the Customer role. They see only their project: the test cases in plain language, the results and the evidence. They can also run acceptance tests by hand.
Each client gets its own project, with its own test suite, environments and encrypted login details. Run every test before each delivery: on a schedule, from your pipeline, or with one click. Each run has a video and the full logs.
Every test is a plain Playwright file in the project's code repository. Keep running the suite for your client, or hand it over with the project. In both cases the tests keep working, with or without vikingQA.
They add tests as code with the feature. They can review the tests the agent writes, if you want that. Their tools do not change.
Project managers, functional consultants and the client's key users record flows with the browser extension or describe them in chat. They never write code.
It defines the test cases, explores the application, runs the tests and writes the automation. Self-healing tests: when the application changes and a test is out of date, the agent explores again and heals the test. A project that had no budget for a tester still gets a test suite.
Only the projects you share. In those projects a client reads test cases, opens results and evidence, and takes part in acceptance testing. A client cannot see your other clients, your settings or your billing.
No. Seats are for your own team. Clients and external viewers with the Customer role need no seat.
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), and a hand-over is a transfer of that repository.
Yes. Tests run from a fixed IP address that the client can add to an allow-list. Credentials are stored as encrypted variables for each environment.
Yes. The agent does the QA work: it defines test cases, explores the application, writes the automation and heals a test when the application changes. It can add each change by itself, or your developers can review it first.
Start free with your own application. No credit card.
We build vikingQA with a small group of design partners.Join the design partner program