When you record a mobile application directly from an emulator window, Ranorex Studio may treat the emulator as a desktop application instead of a mobile device. This limits object recognition and can make the recorded test unreliable.
Limited object recognition when recording from an emulator window
If you start the Recorder and interact directly with the emulator window, Ranorex Studio may revert to image-based recording. In this mode, actions are recorded using screen coordinates instead of the application’s mobile UI elements.
Coordinate-based actions may fail when:
- The emulator window is moved or resized.
- The screen resolution or display scaling changes.
- The application layout changes.
- A UI element appears in a different position.
Add the emulator as a mobile endpoint
For full mobile automation functionality, configure the emulator as you would a physical mobile device:
- Prepare the emulator for mobile testing.
- Add the emulator as an endpoint in Ranorex Studio.
- Confirm that its status is Connected in the Endpoints pad.
- Instrument and deploy the application under test, if required.
- Set the emulator endpoint as the automation root.
- Create and record the test using the mobile endpoint.
This allows Ranorex Studio to work with the application’s mobile UI elements instead of relying only on screen coordinates.
For the complete workflow, see Run a Mobile Test and Add an Android/iOS Endpoint.
When image-based recording is appropriate
Image-based recording may be useful when an application element is not available through object-based recognition. However, tests that rely on images or coordinates are more sensitive to visual and layout changes.
When possible, connect the emulator as an endpoint and use object-based mobile automation for more stable identification and test execution.