XPath in Appium: Tutorial

Locating UI elements accurately is one of the most critical parts of roving test mechanisation. In Appium, testers much rely onXPath, an XML-based locater strategy, to name elements when IDs or handiness labels aren ’ t available. While XPath is powerful and flexile, it also comes with execution trade-offs.

This article explains XPath in Appium, its strengths and drawback, how to implement it in scripts, and best praxis for authentic mobile test mechanization.

What is XPath?

Before become into the specifics, it is necessary to understand what exactly an XPath is and how it aid as a locator.

XPath is nothing but XML Path or an face language that is used to query or transform XML documents. The XPath consists of the following properties:

1. One of the many ways to locate in web or mobile applications
2. Xpath is a World Wide Web consortium recommendation.
3. Xpath has a path-like syntax that helps in navigating through the UI elements of an coating.

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Even though Xpath is one of the locators for UI elements, it is not one of the conventional choices of many Quality Assurance professionals or Mobile/Web app testing professionals. Let ’ s examine some of the advantages and disadvantages of using Xpath in testing.

Advantages and Limitations of using XPath

How do you use Xpath in Appium?

In a conventional setting, you may experience to go through the undermentioned steps & # 8211; not necessarily in the exact order.

1. Getting the started
2. Creating the desired capableness
3. Choosing the environs, OS, etc.
4. Starting up the Emulator through the
5. Creating a examination script in a different environment
6. And making sure all the system dependence and examination dependencies are already installed and scat.

To avoid this, you can simply use by following the steps written below.

Step 1, or you can also upload your own covering. Using the undermentioned Python script.

[python] import petition files = {'file ': open (r ' C: \Users\waseem k\Downloads\WikipediaSample.apk ', 'rb '),} answer = requests.post ('https: //api-cloud.browserstack.com/app-automate/upload ', files=files, auth= (`` mohammadwaseem_r3b75X '', `` JxCJvHgZM5cxPrir6zHS '')) print (response.content) [/python]

Step 2The output will give you a URL for the application that you feature upload. You will use that URL in the hand given below to run a sampling build using Appium and Xpath.

Step 3Use the undermentioned Python Script to run the Appium test using Xpath.

[python] from appium signification webdriver from appium.webdriver.common.mobileby import MobileBy from selenium.webdriver.support.ui meaning WebDriverWait from selenium.webdriver.support import expected_conditions as EC import clip desired_cap = {# Set your admittance credentials '' browserstack.user '': `` '', '' browserstack.key '': `` '', # Set URL of the application under test '' app '': `` bs: //c700ce60cf13ae8ed97705a55b8e022f13c5827c '', # Specify device and os_version for prove '' device '': `` Google Pixel 3 '', '' os_version '': `` 9.0 '', # Set other BrowserStack capabilities '' project '': `` First Python project '', '' build '': `` browserstack-build-1 '', '' name '': `` first_test ''} [/python]

Step 4The sample test will establish the application on the device and search for the keyword given in the playscript. And in the end, add Asserts for the result in the list.

[python] # Initialize the remote Webdriver using BrowserStack remote URL # and coveted capableness defined above driver = webdriver.Remote (command_executor= '' http: //hub-cloud.browserstack.com/wd/hub '', desired_capabilities=desired_cap) # Test case for the BrowserStack sampling Android app. # If you get uploaded your app, update the exam case here. search_element = WebDriverWait (driver, 30) .until (EC.element_to_be_clickable ((MobileBy.XPATH, `` (// * [(@ content-desc='Search Wikipedia ')]) [1] ''))) search_element.click () search_input = WebDriverWait (driver, 30) .until (EC.element_to_be_clickable ((MobileBy.XPATH, `` (// * [(@ text='Search Wikipedia ')]) [1] ''))) search_input.send_keys (`` Browserstack '') time.sleep (5) search_results = driver.find_element_by_xpath (`` // * [(@ resource-id='org.wikipedia.alpha: id/page_list_item_container ')]) '') assert (len (search_results) & gt; 0) # Invoke driver.quit () after the examination is done to indicate that the test is complete. driver.quit () [/python]

Step 5 You can display the resolution in the dashboard, as seen below.

As you can see, the logarithm show how the application was launched, and one of the elements was situate expend the XPath.

Conclusion

There is no hard and fast pattern for using any specific selector to locate a UI element in a web or peregrine application. So is the case with Xpath, be it in Appium or selenium. As a wise QA professional, you must perpetually trust on undertaking requirements and, free-base on those, create your testing strategy. Even though XPath in test scripts may not be a wise choice in the QA community, Appium salvage the day.

Related Guides