
Recording Live
Create a new Test
From the Tests page, click Create test in the top right. Fill in the creation modal:- Test Name: a descriptive name for your test
- Platform: iOS or Android
- App: select an existing app, or create one inline
- Tags: optional labels for filtering (e.g.,
smoke,regression) - Advanced Settings: AI config and YAML import (optional)
Start the Recording
- Start the device by clicking on the device screen or clicking the
Startbutton - Click the Record button
- Interact with the device: tap buttons, type text, swipe, navigate
- Click Stop when you’re done
Reviewing Generated Steps
After recording stops, a review panel shows each generated step with:- Step type (instruction, validation, manual) that you can toggle
- Description in plain English, editable inline
- Confidence score from the AI
- Retry with feedback if the results aren’t right (“focus on the login flow”, “ignore the settings detour”)
- Copy as YAML for use in CI/CD
- Save as module to reuse the steps across tests
Session Compile
Session compile takes your raw device interactions and uses AI to generate structured, natural-language test steps. Explore your app freely, then let Revyl turn that exploration into a test you can run again.How It Works
- Start a session and interact with your app normally
- Stop the session (or let it idle-timeout)
- From the sessions history, click Make a test on any session that has recorded actions
- Revyl’s AI analyzes your actions, groups them into logical steps, and generates natural-language instructions
- Review the generated steps in the editor as described in Reviewing Generated Steps.
The Compile Pipeline
The compile runs through several stages:Queued > Preparing > Summarizing > Merging > Formatting > Complete
Each stage shows progress. If you close the modal while it’s running, a badge appears so you can come back to it.
Partial Compile
You don’t have to compile the entire session. Select a time range to compile just a portion, which is useful for long exploratory sessions where only part is relevant.Tips
- Testing via recorded sessions works best when:
- You’re exploring a new feature and want to turn that exploration into a regression test
- A QA team member found a bug manually and wants to create a reproducible test
- You want to bootstrap tests quickly without writing steps from scratch
- Keep recordings short and focused on a single flow. It’s easier to record login, then record checkout, than to record everything at once.
- The AI works best when your actions are intentional. Avoid aimless scrolling or backtracking during a recording.
- You can record multiple times and build up a test incrementally.