Record the flow in your browser, or describe it in chat. The vikingQA agent turns it into a test that runs on every release, so a broken process is caught before your users see it. You never write code.
Click through your application as usual. The recorder writes down each step.
Open the vikingQA side panel in Chrome and click through the process as you do every day. The extension records each step. The agent turns the recording into a test case and an automated test. Prefer to write? Describe the flow in chat and the agent does the clicking.
The agent reads the ticket in Jira or Linear and the specification in Confluence, Notion or Google Drive. It proposes test cases for each acceptance criterion. You read them in plain language: a title, a description and the steps. You keep, correct or reject each one. The agent writes the code. No developer needed.
Some checks need a person: a printed layout, a new feature, a sign-off. Run the test case by hand with the extension. It follows you through the steps and captures your notes, a video, the console log and the network log. Your result sits next to the automated runs.
No developer needed. Anyone on your team can accept a change in vikingQA, or vikingQA can add and heal tests by itself. You choose. When your team has developers, they see your recorded flow as code in the shared repository. Nobody asks you to read code, and nobody asks them to guess your process.
The agent is a QA colleague. Tell it what to test, the way you would tell a new team member. It asks when something is unclear, explores the application, and comes back with test cases that you can read and correct.
No. You click through the application or describe the flow in chat. You read test cases as a title, a description and steps. You never see code unless you want to.
Yes. No developer needed. Anyone on your team can accept a change in vikingQA, or vikingQA can add and heal tests by itself. You choose. Run your tests on vikingQA, on your own infrastructure, or both.
The vikingQA extension for Chrome. It opens as a side panel next to your application.
Your steps in the application you record, your notes, a video of the tab, the console log and the network log. It records only while you have a recording or a manual run open.
Each test case is written in plain language, so you can read it. Correct a step, or tell the agent what is wrong in chat, and it updates the test. Your team can also choose to review each change before it joins the suite.
Yes. Invite them with the Customer role. They see only the project you share and use no seat. Seats are for your own team.
The agent turns it into a test your team can run every day.
We build vikingQA with a small group of design partners.Join the design partner program