{"id":1676,"date":"2014-10-13T01:04:07","date_gmt":"2014-10-13T05:04:07","guid":{"rendered":"http:\/\/qxf2.com\/blog\/?p=1676"},"modified":"2019-06-27T03:37:58","modified_gmt":"2019-06-27T07:37:58","slug":"appium-tutorial-python-physical-device","status":"publish","type":"post","link":"https:\/\/qxf2.com\/blog\/appium-tutorial-python-physical-device\/","title":{"rendered":"Appium tutorial: Execute Python tests on mobile devices"},"content":{"rendered":"

This Appium tutorial will show you how to run automated tests on a real physical device. We estimate skimming through this post will take you 10 minutes. We estimate working through this post, step by step, will take you about 90 minutes. In this post we will cover getting setup with Appium, interfacing with real devices, writing and running Appium tests. We also briefly introduce you to multiple ways to locate UI elements.<\/p>\n

NOTE:<\/strong> If you have an Android phone handy, you can follow along easily. If not, you may be interested in a previous post showing you how to get started with Appium on an emulator<\/a>.<\/p>\n

\n

Why this post?<\/h3>\n

There are two compelling reasons for this post.
\n1. Mobile devices are taking over the world<\/u>
\nIn recent times there is a lot of interest in mobile testing. And rightly so. The mobile space is growing. The apps are the new cool thing. The mobile space is ideal for software testers looking to learn new things and keep current.
\n2. Lack of high quality tutorials on mobile automation<\/u>
\nOne big challenge in the mobile automation space is the the limited amount of information about the technologies. Quality sources of information on mobile automation is very limited.<\/p>\n

So here is a high quality and informative tutorial for the hands-on tester who wants to get started with Appium and mobile automation on a physical mobile device.<\/p>\n

\n

Why Appium?<\/h3>\n

There are quite a few number of tools out there in the mobile automation market like MonkeyTalk<\/a>, Calabash<\/a>, Robotium<\/a>, etc. Each has its own advantages and limitations. Some of these tools require an agent to be installed, the application has to be recompiled so that the tool can interact with the mobile app, etc. However Appium<\/a> is built on the idea that testing native apps shouldn’t require including an SDK or recompiling the app. Appium is also an open source project – so if you are not happy with it, you can contribute and enhance it. Appium tests run against both on iOS and Android. For me, Appium (while still being extremely immature), looks to be the standout technology that will own the mobile UI automation space. Appium reminds me of the early Selenium versions I used. Based on history, I think Appium will be the front-runner in the mobile UI automation space.<\/p>\n

\n

Step by step Appium tutorial<\/h3>\n

We have already shown you how to run an Appium test using an emulator in one of our previous<\/a> posts. In this post, I will show you how to test an app using a real device. Being a tennis fan, I decided to test a tennis app. On my Android phone, I downloaded the ATP\/WTA<\/a> app and decided to automate some of the functionality of this app. I will also show you how to navigate through different pages in the app using different locator strategies, get data from a table using Appium and Python and how to use the uiautomator<\/a> to find UI components of the page.<\/p>\n

Overview<\/strong>
\n1. Appium setup
\n2. Connect to an Android device
\n3. Select an app to test, get its package and activity name
\n4. Use uiautomatorviewer to find UI components of the application
\n5. Write the test
\n6. Start and launch Appium server console
\n7. Run the test
\n8. View the test result<\/p>\n

STEP 1: Appium setup<\/strong>
\nDownload and install Android SDK<\/a> and Appium<\/a> along with Appium’s client libraries<\/a> for Python. Installations are fairly straight forward. However if you need help, please refer to the setup section in our previous<\/a> blog for a more detailed process on how to set up Appium on your machine.<\/p>\n

STEP 2: Connect to an Android device<\/strong>
\nYou have to enable USB debugging in your phone to be able to run your test scripts. For this, first, you need to enable “Developer options” by navigating to Settings\/About Phone and tapping build number seven times. You will get a notification saying that you’re now a developer. Ignore it – you are still a tester ;). Once you are a developer you need to navigate to “Developer options” and enable the USB debugging option. You can refer to this link<\/a> for more details<\/p>\n

\"Build<\/a><\/p>\n

\"Enable<\/a><\/p>\n

\"Developer<\/a><\/p>\n

Note: On some devices, you may have to download some device drivers to connect your phone to the PC<\/p>\n

STEP 3: Select an app to test, get its package and activity name<\/strong>
\nYou can go to Google Play Store and download the ATP\/WTA<\/a> app. We will automate some of the functionality like navigating to the ATP Singles Rankings view to assert that Novak Djokovic is the first player listed and also get his personal details from the table in players view.<\/p>\n

In order to start the app we would need the app Package and Activity name. We can get these details from the apk<\/a> file of the app. Instead of downloading the apk file and looking into app manifest<\/a> file for this detail, we can also download some really cool apps which can get you these details. Apk Info<\/a> is one such app which you can download from Play Store and get the app Package and Activity details. Just download the app and click on Apk Info Icon which will list all the apps on your device. Click on your app to get the details required as shown below<\/p>\n

\"APK<\/a><\/p>\n

\"Details<\/a><\/p>\n

STEP 4: Use uiautomatorviewer to find UI components of the application<\/strong> uiautomatorviewer is a GUI tool to scan and analyze the UI components of an Android application. To click or to navigate to any components in your app you need to identify the UI components of your application. Using uiautomatorviewer you can take the snapshot of the UI screen on any Android device that is connected to your machine. You can then inspect the layout hierarchy and view the properties of the individual UI components that are displayed on the device.<\/p>\n

Connect your Android device to your machine and open the app you are testing. In your machine open a terminal window and navigate to the path $android-sdk \/tools<\/em> and run the command to open Uiautomatorviewer<\/p>\n

$ uiautomatorviewer\r\n<\/pre>\n
To capture a screen, click the “Device Screenshot button” in the uiautomatorviewer tool. The screenshot of the page in your device is captured. You can move over the snapshot in the left-hand panel to see the UI components identified by the uiautomatorviewer. You can view the component\u2019s properties listed in the lower right-hand panel, and the layout hierarchy in the upper right-hand panel.
\n\"UI<\/a><\/p>\n
STEP 5: Write the test<\/strong>
\nWe will launch the ATP WTA app using the package and activity name we found out and then navigate through various pages using different locator strategies. While we do not recommend using multiple locator strategies, we are doing so in this tutorial only to make you aware of your options. Then we will confirm that Novak Djokovic is the top player listed in ATP Singles Rankings list view and get his personal details from a table in Players view.<\/p>\n
\"\"\"\r\nQxf2: Example script to run one test against ATP_WTA app using Appium\r\nThe test will navigate to ATP Singles Rankings list and confirm that Novak\r\nDjokovic is the top player listed and get his personal details from a table.\r\n\r\n\"\"\"\r\n\r\nimport unittest, time, os\r\nfrom appium import webdriver\r\nfrom time import sleep\r\n\r\nclass Android_ATP_WTA(unittest.TestCase):\r\n    \"Class to run tests against the ATP WTA app\"\r\n    def setUp(self):\r\n        \"Setup for the test\"\r\n        desired_caps = {}\r\n        desired_caps['platformName'] = 'Android'\r\n        desired_caps['platformVersion'] = '4.4'\r\n        desired_caps['deviceName'] = '$ Your device name'\r\n        # Since the app is already installed launching it using package and activity name\r\n        desired_caps['appPackage'] = 'atpwta.live'\r\n        desired_caps['appActivity'] = '.activity.Main'\r\n        # Adding appWait Activity since the activity name changes as the focus shifts to the ATP WTA app's first page\r\n        desired_caps['appWaitActivity'] = '.activity.root.TournamentList'\r\n        self.driver = webdriver.Remote('http:\/\/localhost:4723\/wd\/hub', desired_caps)\r\n\r\n    def tearDown(self):\r\n        \"Tear down the test\"\r\n        self.driver.quit()\r\n\r\n    def test_atp_wta(self):\r\n        \"Testing the ATP WTA app \"\r\n        self.driver.implicitly_wait(30)\r\n        time.sleep(5)\r\n        \r\n        # click on Navigation Bar MainMenu by finding element by xpath\r\n        menubar = self.driver.find_element_by_xpath(\"\/\/android.widget.Spinner[@resource-id='atpwta.live:id\/NavBarMainMenuSpinner']\")\r\n        menubar.click()\r\n        \r\n        # From list of options available click on Rankings by finding element using uiautomator\r\n        rankings = self.driver.find_element_by_android_uiautomator('new UiSelector().text(\"Rankings\")')\r\n        rankings.click()\r\n        \r\n        # click on ATP Singles by finding element using id\r\n        singles = self.driver.find_element_by_id('atpwta.live:id\/RankingsListItem')\r\n        singles.click()\r\n\r\n        # Assert that Novak Djokovic is the top listed player\r\n        elmnt = self.driver.find_element_by_id('atpwta.live:id\/Player1TV')\r\n        self.assertEqual('Novak Djokovic', elmnt.get_attribute('text'))\r\n        print elmnt.get_attribute('text')\r\n\r\n        elmnt = self.driver.find_element_by_xpath(\"\/\/android.widget.LinearLayout[@index=0]\")\r\n        elmnt.click()\r\n        \r\n        # Print the contents of Table listed for the top ranked player\r\n        table = self.driver.find_element_by_android_uiautomator(\"new UiSelector().className(android.widget.TableLayout)\")\r\n        rows = table.find_elements_by_class_name('android.widget.TableRow')\r\n        for i in range(0, len(rows)):\r\n            cols = rows[i].find_elements_by_class_name('android.widget.TextView')\r\n            for j in range(0, len(cols)):\r\n                print(cols[j].get_attribute('text')+\" -- \"),\r\n            print(\"\")\r\n      \r\n               \r\n#---START OF SCRIPT\r\nif __name__ == '__main__':\r\n    suite = unittest.TestLoader().loadTestsFromTestCase(Android_ATP_WTA)\r\n    unittest.TextTestRunner(verbosity=2).run(suite)\r\n\r\n<\/pre>\n
STEP 6: Start and launch Appium server<\/strong>
\nStart Appium server console by double-clicking on the Appium file. Click on the \u2018rocket\u2019 icon to launch the Appium node server.
\nPlease refer to the 6th and 7th step of our previous<\/a> blog if you need more details on starting appium server.
\n\"Start<\/a><\/p>\n
STEP 7: Run the test<\/strong>
\nYou can run the test any way you like. We will run it using the command prompt. The app gets launched in your device and navigates to a different screen.<\/p>\n
\"ATP<\/a>\"Players<\/a>\"ATP<\/a><\/p>\n
STEP 8: View the test result<\/strong>
\n\"BrowserStack<\/a><\/p>\n
\n
Game. Set. Match. You learnt how to do mobile automation using Appium on a real device! If you are still hungry for more, take a tour of our open-sourced web and mobile automation framework<\/a>.<\/p>\n
\n