Product
Solutions
Pricing
Resources
Customers Support
Company
Book a demo
Test environments

A fresh account and app copy for every run

Tests are only as good as the place they run. Every QA run gets its own copy of your app, built from the exact commit, and signs in as a brand new user. No shared admin account, no leftover data, no runs getting in each other’s way.

$ qa --pool-status slot 1 busy SHOP-482 build 9f2c1a slot 2 busy SHOP-490 build 9f2c1a slot 3 free healthy build 9f2c1a slot 4 free healthy build 9f2c1a Test account: new company, location and user Two factor sign in handled
Isolated by default

Why separate copies matter

Built for every change

Each run uses a copy of your app built from the exact code being tested.

Never restarted mid run

A busy copy is never touched. Free copies move to the newest build when they are released, after a health check.

Two to four runs at once

Each run reserves its own copy with its own address, so several tickets are tested at the same time.

Real users, not admins

Tests sign in like your customers do

Before testing, the agent creates a new company, location and invited user over your API, finishes sign up in the browser, and handles two factor sign in. The test sees exactly what a new customer would see.

  • Different roles for different tests
  • Everything created is listed in the report
Third party services

Connected services are tested for real

When a feature depends on a connected service, such as an accounting or printing tool, the agent connects a sandbox account for that test. Credentials stay in a secure store and there are guards against deleting anything real.

  • A real verdict instead of "could not test"
  • Credentials kept out of your code

Questions

Do we need our own servers for this?

The app copies run on a machine we set up with you. For founding customers we handle this as part of setup.

Can it test against our existing staging?

Yes. Without separate copies it runs against one environment you choose, one run at a time.

Fire your QA backlog,
not your team

Let agents test every pull request, keep your regression suites green and send your team clear reports, videos and bug tickets.