How to use Accessibility Insights and Locator Types with Native Apps
To use Cycle native app steps, it is recommended that Windows Accessibility Insights is installed to identify app Object Identifiers. If you have not downloaded and installed Accessibility Insights, follow the instructions provided in this page:
When using native app steps there are 4 element locator types that can be used to interact with applications using Cycle.
Finding Object Identifiers with Accessibility Insights:
1) With your application and Accessibility Insights open, the mouse cursor can be moved around the application and Accessibility Insights will show UI element information in real time based on what UI element the cursor is hovering over.
In the example below using Windows calculator app, the “1” button is being hovered over, and the Live Inspect view displays information about the “1” button. The Tree view shows the location of the button within the element hierarchy, and the Details section shows Object Identifiers of the button.
The default view on the details pane does not show all possible properties of an object. To update this, click the gear symbol on the Properties section header and check the box for "Include all properties that have values":
2) The Tree view on the left side can be navigated to any accessible element within the element hierarchy with mouse or keyboard.
Both a Locator Type and an Object Identifier are needed in order to write Cycle steps.
For most use cases the Name or AutomationId object types will be the most reliable and help maintain the readability of features. Using xPath and controlType may take more time to execute and could be less reliable.
Note: If an application is closed and reopened, Accessibility Insights may also need to be closed and reopened in order for accurate information to be displayed.
Accessibility Insights has a wide range of additional settings and features, the official Microsoft documentation can be found here: