QA Tester

QA Tester is a CloudAxis specialist that explores your product for broken or confusing flows, and can also run saved automated test scripts on a schedule to catch regressions before customers do.

What QA Tester does

In chat, QA Tester explores a flow you point it at — signup, checkout, a settings page — and reports every broken step, confusing interaction, or visual issue it finds, with screenshots. On a schedule, it switches to a narrower automated mode: running saved test scripts against public URLs and reporting pass/fail with screenshots on failures, using code execution to drive the checks.

QA Tester keeps task records of prior runs, so a weekly regression report can point directly at what's new since last week instead of restating every check that still passes.

Good for

Free-form exploration of a staging environment before a release, listing every rough edge a real user might hit.
A saved regression suite that reruns automatically and flags anything that broke since the last pass.
Spot-checking a specific detail after a change, like confirming checkout still shows the right tax line for a region.

What it needs connected

QA Tester doesn't require a Launchpad integration to start — it tests public URLs using the cloud browser and code execution. It works best against pages that don't require a login for its scheduled runs; use chat directly for flows that need authentication.

Typical duties

QA Tester ships with a weekly regression duty by default, commonly Monday morning, that reruns your saved checks and reports what changed since the previous week. You can add more duties for other flows or trigger any of them manually after a deploy.

What you can ask in chat

"Explore our staging signup flow and list every broken or confusing step."
"Rerun the saved regression checks and tell me what's different from last week."
"Does checkout still show the right tax line for EU customers?"

Plan

QA Tester is available from the Growth plan.

Limits

QA Tester's scheduled runs are narrow and public-URL only by design — logins, exploratory testing, and full compliance test matrices need a human in the loop, either reviewing results or working with QA Tester directly in chat.

Frequently asked questions

Does QA Tester replace a full compliance test suite?

No — its default weekly duty is a narrow regression pass over public URLs. Broader or compliance-grade testing should keep a human reviewing results alongside it.

Can QA Tester test flows behind a login?

Yes, but that's better handled by working with it directly in chat rather than through its scheduled public-URL duty.