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
Support

Real people, quick answers

You talk to the people who build GreatQA. Email us, or book a call if it is easier to show us.

Email us

Write to [email protected]. We reply within one working day, the same day for founding customers.

Book a call

Walk us through it on a call, sharing your screen.

Ask for a call

Read the docs

How GreatQA works, what it needs and every qa command.

Open the docs
Questions

Common questions

A run came back Blocked. What now?

The report names what blocked it, for example a third party sandbox that was down. Fix or wait out the blocker, then rerun with qa --continue.

A run never posted anything.

It may be waiting for the other half of a feature, or paused until your AI usage limit resets. Run qa --holds and qa --log to see why.

Can I change what a run tested?

Yes. Use qa --continue with a correction in plain words, for example "also test it on a phone screen".

How do we request an integration?

Email us or use the contact form. Founding customers decide what we build next.

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.