What shipped.

Your tests can now start on every deployment and report the result back. The pipeline API starts a batch of tests from any CI system, and your pipeline can fail when a test fails. Authenticate with a project API token, which you create in the project settings, and name the environment to run against. Pass tags to run only part of the suite.

A project now starts from your code repository. Connect GitHub or GitLab and vikingQA lists the Playwright tests it finds as your test cases. When the agent writes or changes a test, vikingQA adds the change to your test suite by itself, or your team reviews it first as a pull request.

A test run now opens on its own page, with its own link, instead of in a window over the page you came from. Share the link, or open a run in a new tab from the results list, the batch page or the test case. The back button returns you to where you were.

Pick any test case in the browser extension and run it yourself, in your own browser. The extension captures your steps, your notes, a video of the tab, and the console and network logs. When you finish, you mark the run passed or failed, and it appears in the test results with every other run.

Runs and agent sessions can now reach your application from one fixed IP address per project: your own proxy, or one we provide. Add the address to your allow-list and vikingQA can test an application behind your firewall. Turn it on in the project settings, under Network. If the fixed address is not available, the run stops instead of using another address.