Your tests run by themselves each time your team releases, or at the times you set. A failed test can stop the release, and the result waits in one place with its video. Run the tests on vikingQA, on your own infrastructure, or both.
Connect vikingQA to the way your team already releases. From then on, each release is checked, and nobody starts a run by hand.
Your delivery pipeline starts the tests when a new version is deployed, and waits for the answer.
vikingQA starts the tests by itself when a change is proposed, and shows the result on the pull request before the change is merged.
Put the tests in front of your deployment, and a release with a failed test does not go ahead. Or let the release continue and read the result. You choose.
Each run keeps its video and its logs in vikingQA. The answer to your pipeline has a link that opens the result.
No pipeline yet? A schedule runs the same tests at the times you set and emails a summary to the people you name.
There is nothing to install. It works with GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, CircleCI and any other pipeline tool. You can also run the same tests on your own infrastructure.
After a deployment, your pipeline tells vikingQA which environment to test.
The tests run in the vikingQA cloud, each in its own isolated browser, with video and logs.
Passed or failed, with a link to the result. Your pipeline continues or stops.
Any pipeline tool that can call a web address. The docs have a complete guide for GitHub Actions. The same steps work in GitLab CI, Jenkins, Azure Pipelines and CircleCI.
No. Running your committed Playwright tests costs no AI credits.
Yes. Your pipeline can select tests by tag, such as your smoke tests. Without tags, the full suite runs.
Yes. The suite is plain Playwright in your repository. Use vikingQA runs when you want the evidence, the reports and the shared results in one place.
After the change is merged. You merge it yourself, or you turn on automatic merge and vikingQA merges it for you. A merged test is in the next run.
Use fixed-IP egress and add one address to your allow-list. Private runners inside your network, for when no inbound access is possible, are on our roadmap.
Start free with your own application. No credit card.