Product
Tests every changeRegression suitesReportsNarrated videosPhone and tablet screensHow it worksIntegrationsTest environmentsSelf-growing automationsScreen recordingChangelog clipsYour AI provider
Use cases
Engineering teamsQA teamsProduct managersMarketing and supportStartupsScale-upsEnterprise
Customers
GreatLabKitLegitAll customersFounding customers
Pricing
Resources
DocumentationQuick startCommand lineWriting regression testsSupportAbout usFounding customersContactCareers
Book a demo Try for free
Documentation

Quick start

Your first QA run, from setup to report.

1. Connect your tools

We connect your code host, ticket system, docs and team chat, and set up a test environment of your app. For founding customers we do this with you on a call.

2. Run your first test

From a branch with changes, run:

$ qa

It compares your branch with the main branch, reads the ticket if the branch name contains one, creates a fresh test account and tests the change.

3. Try the other ways to start

$ qa --ticket SHOP-482
$ qa --pr 1290
$ qa --scenario "a new user can apply a discount code at checkout"

4. Read the report

When the run finishes you get a report in your docs, links on the ticket and a message in your team chat. Every run is kept in its own folder, which you can list with qa --sessions.

5. Correct a run

$ qa --continue "also test the empty state on a phone screen"

This continues the same session, reruns the test and rewrites the report.

6. Turn on automatic testing

Schedule qa --sync every 30 minutes. It picks up new merges, builds once per commit and starts runs in the background.

You build the product.
Your QA employee checks it.

Show us your app. We'll run GreatQA on a real change of yours, live on the call.