Skip to main content

​
Common Issues

Fix: Make test description more specific. Instead of “Click submit”, use “Click the blue Submit button at bottom of form”.AI needs clear targeting. Add unique identifiers in descriptions.
Fix: Check environment variables. Add secrets (API keys, auth tokens) in dashboard Settings → Environment.Also verify base URL matches your staging/production environment.
Fix: Be explicit in test description. Say “Verify order total equals $49.99” not just “Check total”.Re-run test generation with clearer requirements.
Fix: Tests have 5-minute timeout. Break long flows into multiple shorter tests.Example: Separate “login” and “checkout” into two tests.
Fix: Verify GitHub App has “Pull requests: Read & Write” permissions.Reinstall app if needed: github.com/apps/rehearsal-ai
Fix: Add explicit waits. In test description: “Wait for spinner to disappear, then click Next”.Rehearsal auto-adds waits, but complex apps need hints.
Yes. Use ngrok or similar tunnel. Point test to public URL.Or contact us about self-hosted runners: support@rehearsal.ai
Two options:
  1. Include login in each test description
  2. Use test setup with saved cookies (contact support for this feature)

​
Pricing & Limits

Free tier:
  • 10 tests/month
  • 50 test runs/month
  • Community support
Pro ($49/mo):
  • Unlimited tests
  • Unlimited runs
  • Priority support
  • Custom test suites
Enterprise:
  • Self-hosted runners
  • SSO/SAML
  • SLA guarantees
  • Dedicated support

​
Getting Help

Response time: < 2 hours for Pro/Enterprise, < 24 hours for Free tier.