Low Level Recording
Low-level recording in SimplifyQA is an advanced mobile testing feature that captures interactions at the element or coordinate level, rather than relying solely on high-level UI elements. This method is particularly useful when certain elements are not detectable through conventional object recognition methods.
When to use Low-Level Recording?
When UI elements are not identifiable using XPath or accessibility IDs.
For gesture-based interactions like drag, swipe, long press, and coordinate taps.
In hybrid or native mobile apps with complex or dynamic UI components.
For troubleshooting failed recordings caused by object hierarchy issues.


How it Works
When recording a test using the SimplifyQA mobile recorder, if the recorder is unable to fetch an element, the user can switche to low-leve recording.
The recorder will then capture the exact screen coordinates of the tap, swipe, or input action.
These actions are stored and replayed based on screen coordinates rather than element properties.
How to enable Low-Level Recording
Activate Low-Level Recording:
On the right side of the recording interface, click the Low-Level Recording icon.
Perform Required Actions on the Device:
Every tap, gesture, or interaction will now be recorded as coordinate-based actions.
The tool logs each gesture as a separate step in the background.

Adding Validations During Recording:
While recording, press Shift key twice quickly.
A pop-up window will appear listing available validation actions such as:
LowLevel click
Scroll till text if text not present
Scroll till text if text present
Type text
Wait until text is not present
Wait until text is present
Choose the relevant validation from the list.
The selected validation will be recorded as a separate step in the test case.

Review and Save Recorded Steps:
Once actions are captured, SimplifyQA will log them as steps
You can optionally switch back to standard recording to continue element-based recording.
Click Stop Recording once you're done.
The recorded steps will appear in the test case editor, which you can review, re-order, or edit.
Important Notes:
Low-level steps are more fragile to UI layout changes, so use them only when element identification fails.
You can mix standard and low-level steps in a single test case.
Coordinate-based validations or inputs should be tested across screen resolutions if using cloud/mobile farms.
Frequently Asked Questions (FAQs)
Last updated
