- Visual Editor: Build steps by hand in the Revyl UI
- Recorded Session: Interact with the app yourself and Revyl generates the steps from your recording
- Agent Based: An AI agent writes the test for you using the Revyl CLI
Testing Best Practices
- Prefer natural-language, intent-driven instructions over long, granular steps. This keeps tests less brittle as your app changes over time.
Recommended
- Go to Settings and enable notifications if they’re currently off.
Avoid
- Step 1: Tap the hamburger menu icon in the top-left corner (should be at approx x=20,y=40)
- Step 2: Wait exactly 2 seconds
- Step 3: Tap “Settings” which is the 3rd item in the list
- Step 4: If a modal appears, tap the X in the top right, otherwise proceed
- Step 5: Scroll down exactly 2 screen-heights
- Step 6: Tap the toggle next to “Notifications” only if it’s currently off
- Bypass authentication for tests that aren’t testing auth. Authentication can take a long time to run on every test, so for flows that don’t specifically test it, bypass authentication with deeplinks instead.
- Whitelist Revyl’s IP addresses if your app has rate limiting or CAPTCHA blocks, so they don’t interfere with testing.