Troubleshooting¶

The app under test must be reachable¶

For cloud execution, your target URL must be reachable over the public web.

If your app is behind a firewall, VPN, IP allowlist, or private network, runs may fail to load pages.

Quick checks

Try opening the URL from a different network/device
Confirm your environment is reachable without internal-only access

The UI must be DOM-based¶

Automation finds and clicks DOM elements (buttons, inputs, links, and similar). If your interface is canvas-only, WebGL-only, or otherwise lacks normal DOM nodes for controls, the agent may not be able to drive the app reliably. See Does my app need a DOM-based UI?.

Supported

Open web apps — areas that do not require login
First-party credentials — username/email and password in your app's own sign-in UI

Not supported in the standard product

Third-party sign-in (OAuth, social login, etc.) and SSO
CAPTCHA and similar bot challenges

If your main journey requires SSO or third-party login, you can try a staging environment with first-party credentials, or email support@vibetesting.me to discuss a custom solution.

The test gets stuck early¶

Try:

Reducing steps per flow
Reducing the number of flows
Narrowing focus areas to a single page/feature (e.g. “dashboard” only)
Adding a short guideline like:
“Avoid logout”
“Avoid destructive actions”
“Do not submit payment / do not delete items”

Unexpected results or behavior¶

If the behavior differs from what you expected:

Re-run the suite after your fix
Compare the latest run to a previous run to validate the change and detect regressions

What to send support¶

Include:

Application URL
Run / suite name (or run ID, if available)
What you expected vs. what happened
A screenshot snippet (if you have it) or copied issue text

Contact: support@vibetesting.me