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
Login limitations¶
Supported
- Credentials-based login inside your app (username/email + password)
Not supported (currently)
- SSO / third-party authentication flows (Google, GitHub, Microsoft, etc.)
If your main journey requires SSO, consider using: - a staging environment without SSO, or - a credentials-based test-user flow
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