Testsigma provides a shared UI Identifiers object repository which allows you to share and reuse the UI Identifiers between your Test Cases. This is similar to a Page Object Model and avoids duplication of UI Identifiers. Also, when a page changes, it is helpful for the testers to manage UI Identifiers without modifying the Test Scripts directly.
We can navigate to the UI Identifiers page by going through Test Development > UI Identifiers
The landing page looks as given below:
Please check the below article to know more about managing UI Identifiers:
How to manage(create/edit/delete) UI Identifiers?
Creating UI Identifiers manually
Clicking on the Create button on the top right corner opens the Create UI Identifier page with the input fields mentioned below.
Enter the details as given below:
Name: Enter the name that is used for UI Identifier.
Screen Name: Screen Name will be helpful to group you identifiers by each screen in your application. This helps to you search identifiers in each screen in your application.
Advanced Options: Use advanced options to create an XPath or CSS Selector interactively using the Testsigma UI Identifier creator. Please check the following article for a detailed guide on using Advanced Options - How to create UI Identifier with Advanced Options?
Identifier Type: Select the suitable locator from a drop-down box:
- link text
- partial link text
- class name
UI Identifier: Enter the value for the UI Identifier type you previously selected. Check the following section Getting UI Identifier using Appium Inspector to know how to get the UI identifier for your iOS App using Appium's built-in Inspector.
Finally, click on Create button to finalize the creation. You can see the success notification for the newly created UI Identifier.
Getting the UI Identifier using Appium Inspector
- XCode - Configured for automation of iOS Apps - Configuring your Mac and iOS device for Hybrid Test Execution
- Appium Desktop - Configuring Appium Desktop Inspector to inspect Android/iOS Apps locally
Assuming the prerequisites are satisfied, we can inspect UI Identifiers separately or record all the required UI Identifiers in a single session as shown below: