One workspace

Test engineers, analysts and customers share one workspace.

They work in the same project, on the same test suite. A test engineer writes a test, an analyst records a flow, and a customer runs it and reads the result. A customer sees only the projects you share.

Technical teams

Write tests as code, in their own tools.

  • Developers
  • QA engineers
  • Platform
Business teams

Describe a flow, or click through it. No code.

  • Finance
  • Sales
  • Operations
  • Support
The agent

Your AI QA colleague, for both teams.

  • Writes the tests
  • Runs them
  • Heals them
One shared test suitePlain language · Code
  • A manager approves an invoice above the limitinvoice-approval.spec.ts
  • A customer changes the delivery addressdelivery-address.spec.ts
  • A new employee gets the correct accessemployee-access.spec.ts
Who is in it

Each role adds to the same suite.

The project holds one test list. Whoever adds a test, it shows up there.

01

Test engineers

Developers and automation engineers add tests as code, from the editor and repository they use now. They can review what the agent writes, or vikingQA can add and heal tests by itself.

02

Business analysts

They click through a flow once with the browser extension, or describe it in chat. The agent writes the automated test.

03

Customers

Invite a client or a key user with the Customer role. They see the projects you share.

  • They record a flow or run a test by hand.
  • They read each test case, each result and the video.

Seats are for your own team. People with the Customer role need no seat.

04

The agent

The vikingQA agent writes the test case, explores your application and adds the automated test to the suite. Self-healing tests: when your application changes and a test is out of date, the agent explores again and heals the test. It adds the change by itself, or your team reviews it first.

One suite

Everyone opens the same test list.

A test an engineer pushed, a flow an analyst recorded and a run a customer started sit in that list.

Your tests are stored in your own code repository, in a standard open format. If you cancel, every test stays and keeps running.

  • The test case, in plain steps.
  • The automated test behind it.
  • The result of each run, with its video and the logs.

For developers: Every test is plain Playwright in your git. Cancel tomorrow and you keep every test.

Questions about the shared workspace.

Who can I invite into a workspace?

Your own team joins as Owner, Admin or Member. Clients, key users and external testers join with the Customer role, on the projects you share.

Does a customer take a seat?

No. Seats are for your own team. People with the Customer role need no seat.

What can a customer see?

The projects you share: each test case, each result and the video. They record a flow or run a test by hand. They do not see your other projects, your settings or your billing.

We have no test engineer. Can we still use it?

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.

What happens if we cancel?

Your tests are stored in your own code repository, in a standard open format. If you cancel, every test stays and keeps running.

Catch the next bug before your customers do.

Start free with your own application. No credit card.