- How does it plug into our release?
- Trigger a run from your CI or with one click. If you switch the gate on, a red run blocks the release right away, on the agent's result. A person then reviews each failure, which can take longer than the run, and tells you whether it was your app or our test.
- What access do you need?
- A test account, on staging or production as you prefer, plus a bot-protection exception or a sandbox where needed. Nothing is sent to your real customers, payments run only in a sandbox with test cards, we never train models on your code or test data, and EU data residency with a DPA is standard.
- What about flaky tests?
- A person checks every failure first. When our test was wrong, we fix it and it never reaches your report. The agent can be wrong, so we promise evidence and review, not zero false alarms.
- Who owns the tests?
- They're written in plain language and you can download them. Prefer to run them yourselves later? Switch to a license and keep them.
- What can't it do?
- CAPTCHAs, bot walls and 2FA need a bypass or a test account. It doesn't replace unit tests, and it isn't a penetration test or a legal audit. Native mobile apps are out of scope today.
- Why not let our coding agent write the tests?
- A coding agent tests the code it just wrote. We test your app from the outside, like a stranger, and a person owns every failure.