Check Selenium Interviewquestions from 1 to 10 below:
Check Selenium-SDET-UIAutomation Questions set 21 to 30:
Check Selenium-SDET-UIAutomation Questions set 41-50:
Q&A Set 41-50
Check Selenium-SDET-UIAutomation Questions set 51-70:
Mention the Locator strategies for Mobile Automation?
Mention the locators used for Mobile Automation?
| Strategy | Description |
|---|---|
| Accessibility ID | Read a unique identifier for a UI element. For XCUITest it is the element's accessibility-id attribute. For Android it is the element's content-desc attribute. |
| Class name | For IOS it is the full name of the XCUI element and begins with XCUIElementType. For Android it is the full name of the UIAutomator2 class (e.g.: android.widget.TextView) |
| ID | Native element identifier. resource-id for android; name for iOS. |
| Name | Name of element |
| XPath | Search the app XML source using xpath (not recommended, has performance issues) |
| Image | Locate an element by matching it with a base 64 encoded image file |
| Android UiAutomator (UiAutomator2 only) | Use the UI Automator API, in particular the UiSelector class to locate elements. In Appium you send the Java code, as a string, to the server, which executes it in the application’s environment, returning the element or elements. |
| Android View Tag (Espresso only) | Locate an element by its view tag |
| Android Data Matcher (Espresso only) | Locate an element using Espresso DataMatcher |
| IOS UIAutomation | When automating an iOS application, Apple’s Instruments framework can be used to find elements API Testing Interview Question Set: SeleniumWebdriver Automation Testing Interview Questions:
|
No comments:
Post a Comment