Skip to main content

SeeTestAutomation- Non-Instrumented Native Recognition

info

Please note that this tool is classified as a Legacy tool. We recommend transitioning to our updated solutions to maintain optimal performance and security in your workflows. For more information on this matter, please reach out to technical support .

SeeTestAutomation can also recognize some Native elements in non-instrumented applications/screens on devices running under either:

  • iOS 7 or above

  • Android version 4.1 or above

    For This capability is particularly useful when creating automated test scripts which involved the settings of the devices.

info
  • In iOS, to be able to take advantage of SeeTestAutomation's non-instrumented Native Recognition capability, you must first set the non-instrumented mode on the device (which requires iOS sign configuration. Please refer to Connecting an iOS Device
  • In Android, SeeTest supports dumping UI elements that have accessibilityNodeProvider. Custom views do not provide the accessibility to elements nodes by default. Therefore, if they don't have accessibilityNodeProvider implemented for them, SeeTest will not be able to retrieve non-instrumented dump from them. For example, Samsung/LG devices' system-keyboards do not provide this accessibility. In this case, if you wish to retrieve dump from keyboard, you will need to download another keyboard from playStore that is accessible - such as Google's Keyboard and set it as your default keyboard on these devices. As for non-system apps, you can retrieve instrumented dump, instead, for native recognition, after you instrument the app.

When using non-instrumented Native Recognition, SeeTestAutomation's Object Spy will highlight the application's elements by placing them in yellow rectangles, as can be seen below.

You can utilize such non-instrumented Native elements just as Native elements are defined for instrumented applications, meaning that you can use them to test the application by either:

  1. Dynamically defining them during the recording of a test script, by assigning each such property the value "NATIVE" for its Zone, or
  2. Refining their definition later on through SeeTestAutomation's Repository by making them properties of different types and for different devices under the Native tab of the Object/Element Properties dialog box.
Last updated on