Talk to the people who built it

There is no form on this page and no ticket queue behind it. Every button on this site opens your own mail client, and a message to the address below is read by an engineer.

Three ways in

• hello@qaright.comFor anything: a question before you sign up, a bug, a walkthrough, Enterprise pricing, or deleting your account. We keep your message and address for one reason — to reply — and we do not add you to a list.
• The communityA public board you can read without an account. Ask how something works, or whether someone else has hit the same thing; answers are searchable afterwards, which an email thread is not.
• Contact us, inside the appIf you are signed in, the "Contact us" link in the sidebar sends a message with your account and workspace already attached, so you do not have to explain which one you mean. Pick a topic — a question, something broken, an idea — and write.

Reporting a bug

Most reports can be reproduced first time if they carry three things:

• The browser you were running the test in — Chromium, Firefox or WebKit, and headed or headless.
• A link to the test run. The run report holds the step list, the screenshots, the timing and every repair the engine made, which is almost always where the answer is.
• What changed. If the test used to pass, what moved in the app between then and now — a deploy, a renamed button, a new banner. If nothing changed on your side, say so; that is useful too.

If the problem is a locator the engine could not heal, the healing report on the failing step tells you which cascade phase gave up and why. Paste that in.

Other subjects

Want to see it before you record anything? Book a walkthrough. Evaluating for a regulated environment or a private network? Ask about Enterprise, and read where it runs first. Anything about your data is on the privacy page.