Supported Actions in Reflect Mobile
Reflect supports a core set of user actions for recording and playback on native mobile applications. These supported actions are automatically tracked during a test creation session and translated into AI-generated test steps.
This guide outlines the supported mobile actions: Taps, Swipes, and Keypresses.
Taps
Reflect records all standard tap actions performed on the mobile screen during test creation.
Example AI prompt generated:
Tap on [element-name]
Not Supported:
Warning
Manually adding unsupported tap actions to AI prompts will not work.
Long press
Double tap
Any custom “click” types
Swipes
Swipes are captured when a user performs a click-and-drag gesture on the screen.
Example AI prompt generated:
Swipe [direction] on [element-name]
Swipe Playback Behavior
Swipe uses a fixed magnitude of 40% of the viewport.
Swipe duration is not tracked.
Reflect does not support swipe-until-visible or conditional swiping.
Note
We are actively exploring enhanced swipe support. Contact us with related feature requests or questions.
Keypresses
When a keyboard is triggered during a test recording:
The mobile screen is disabled.
An input box appears at the bottom.
Users can enter text, including variables or dynamic values.
Reflect generates an AI prompt step like:
Enter "some-value" into [input-field]
Playback Behavior
Reflect performs a controlled sequence to ensure stability.
Warning
Not all keyboards can be programmatically hidden. This behavior depends on the app and its framework.
Hide the on-screen keyboard (if possible).
Tap the input field.
Send the text.
Hide the keyboard again (if possible).
Waits
For screens or content with long loading times, or when a pop-up takes longer than expected to close, you can manually add implicit waits with AI prompt steps to help stabilize your mobile test cases.
To add a wait, select the blue button to add an AI step. Use a pattern such as:
"Wait for [object or object state] to be visible". This AI prompt works like an assertion prompt.
For example, if you add "Wait for My profile button to be visible", the AI prompt step searches for the button until the test step times out. If the button never appears, the step fails.
If that outcome is expected, you can make the AI prompt step optional by selecting in the test step description.
Unsupported Actions
The following gestures and interactions are not supported, either via recording or manual AI prompt entry:
Multi-touch gestures (e.g., pinch, zoom, rotate)
Long press
Conditional swipe gestures