The recorder is a Chrome extension. It sits next to your application and watches while you do your work. The vikingQA agent turns what you did into a test your team can run every day. You never write code.
Works in Chrome and Chromium-based browsers. Free with every plan.
Click through your application as usual. The recorder writes down each step.
Click through a flow in your application. The agent turns your recording into a test case and an automated test.
Do the test yourself. The recorder captures what happened. At the end, you say passed or failed and add a note.
You do the test. The recorder writes down the rest.
Each click, each typed value and each page change, in order, in plain language.
Type a note at any moment. It is saved at the point in the run where you wrote it.
A recording of the browser tab you test in.
The errors and messages the page writes while you work.
The requests the page makes, with their status and timing.
Stop the recording and send it. There is no form to fill in.
The agent reads your steps and writes a test case in plain language: a title, what to verify, and the steps. You read it and correct it in chat.
The agent writes the automation in plain Playwright and runs it in the cloud until it passes.
No developer needed. vikingQA can add the test by itself, or your team can review it first. You choose. From then on, the test runs with the rest of the suite, on vikingQA or on your own infrastructure.
Some tests cannot or should not be automated, and the reasons are specific to your business: a judgment call, a physical device, a one-time check, a system that belongs to a third party. vikingQA does not force you to automate them. Run them by hand with the recorder, and each run leaves a record: who ran it, on which environment, the verdict, the note and the evidence.
Pick any test case and run it by hand. The recorder opens next to your application and follows along.
A manual run appears in the same list as the automated runs, with the same statuses.
A failed manual run has the video, the steps and the logs a developer needs to fix the bug.
The recorder starts when you press Record and stops when you press Stop. A run that you close before you submit is not sent.
No. You click through your application. The agent writes the code. No developer needed: vikingQA can add the test by itself, or your team can review it first.
Yes. The recorder runs in your own browser, with your own session. If you can open the page, you can record it.
They do not leave your browser. The recorder replaces each password with a placeholder. When the test runs, it uses the secret that your team stored for that environment.
No. You read the test case in plain language. The code is stored in your team's repository. A developer can review it there, if your team wants that.
Yes. Invite them with the Customer role. They can record tests and run tests by hand in the projects you give them.
Chrome and Chromium-based browsers that install extensions from the Chrome Web Store.
The recording does not. The agent's work to turn it into a test does. Running your committed Playwright tests costs no AI credits.
The agent turns it into a test your team can run every day.