{"id":636,"date":"2014-06-26T09:56:58","date_gmt":"2014-06-26T13:56:58","guid":{"rendered":"http:\/\/qxf2.com\/blog\/?p=636"},"modified":"2024-10-16T16:28:36","modified_gmt":"2024-10-16T20:28:36","slug":"appium-mobile-automation","status":"publish","type":"post","link":"https:\/\/qxf2.com\/blog\/appium-mobile-automation\/","title":{"rendered":"Get started with mobile automation: Appium & Python"},"content":{"rendered":"

Problem:<\/strong><\/span> There is a perception among testers that getting started with mobile automation is hard.<\/p>\n

Why this post? <\/h2>\n

I strongly believe that a tester must have a wide range of skills. You do not need to be an expert in all of them, but it is extremely important to have contemplated a spectrum of concepts and explored a variety of tools. The context under which you test will inform you of the specific choice of testing methodology and test tools to choose. The more options you are aware of, the better your context-specific choice is going to be. In this regard, I began noticing that mobile testing has become somewhat of a niche among testers. Testers are reluctant to get started with mobile testing – probably because they think getting started involves a lot of time and effort. At Qxf2 Services<\/a>, we have decided to tackle the problem head-on. This post is the second in a series of quick, easily consumable tutorials geared towards hands-on testers looking to start exploring the mobile testing landscape. <\/p>\n

NOTE:<\/strong> In this post we are concentrating only on the “getting started” phase. The tools your test team uses to solve the specific and unique problems can greatly vary. There is no one silver bullet.<\/p>\n

\n

A little bit of history <\/h2>\n

On the eve of Christmas 2013, Selenium officially retired<\/a> their own AndroidDriver and iPhoneDriver in favour of Selendroid<\/a>, iosdriver<\/a> and Appium<\/a>. In an earlier post<\/a> we explored using Selendroid and Python. In this post, we will help you get started with Appium.<\/p>\n

Appium <\/a> is an open-source tool you can use to automate mobile native, mobile web, and mobile hybrid applications on iOS and Android platforms. Appium is “cross-platform”: it allows you to write tests on multiple platforms (iOS, Android), using the same API. This enables a large or total amount of code reuse between iOS and Android test suites.<\/p>\n

\n

Appium setup<\/h2>\n

Here are the steps to setup Appium on Windows 7 and use it with Android emulator.
\n1. Download the latest Appium <\/a><\/strong>
\nI have used appium-desktop-Setup-1.5.0-ia32.exe. You can run the exe to install the appium desktop app
\n2. Download and Install Android Studio<\/a><\/strong>
\nOnce you install Android Studio make sure the AVD Manager is also installed as we are going to run our tests on an emulator. Set ANDROID_HOME to be your Android SDK path and add the tools and platform-tools folders to your PATH variable. I could find the Android SDK installed on the below-mentioned path
\n$\\AppData\\Local\\Android\\Sdk<\/strong><\/p>\n

3. Install the Java JDK<\/a><\/strong>
\nSet JAVA_HOME to your JDK folder
\n4. Install the Python client library<\/strong>
\nThere are client libraries (in Java, Ruby, Python, PHP, JavaScript, and C#) which support Appium\u2019s extensions to the WebDriver protocol. When using Appium, you want to use these client libraries instead of your regular WebDriver client. I have used the Appium Python client available here<\/a>. Assuming you have pip installed on your machine, you can use the following command to install it<\/p>\n

pip install Appium-Python-Client <\/pre>\n
Woot! You are now set up. Next stop: launch the emulator and start the Appium server.<\/p>\n
5. Start the Android Virtual Device (AVD) Manager<\/strong>
\nStart the Android Studio and launch the Android Virtual Device (AVD) Manager from by clicking on the link as shown in the screenshot below.
\n\"AVD_Manager\"<\/a><\/p>\n
Create <\/a>an emulator with the preferences you need and launch it using the start button
\n\"android_emulator\"<\/a>
\n6. Start the Appium server console<\/strong>
\nStart the Appium server console by double clicking on the Appium file. <\/p>\n
\"start_appium\"<\/a>
\n7. Launch the Appium node server<\/strong>
\nClick on the ‘rocket’ icon to launch the Appium node server
\n\"Launch_Appium\"<\/a>
\n\"appium_node_server_console\"<\/a><\/p>\n
\n
 Your first test using Appium<\/h2>\n
For this test we will use one of my favorite Android apps – the highly recommended Chess Free<\/a> application created by the UK based AI Factory<\/a>. For this blog post, we will pretend that our test is to launch the application and click on “PLAY” button.<\/p>\n
1. Obtain the .apk for the application under test<\/strong>
\nWe obtained the .apk for Chess Free over here<\/a>. Copy the chess application to a directory of your choice. I used ($Directory_Of_My_Choice\\apps\\Chess Free.apk )
\n2. Peek into the AndroidManifest.xml<\/strong>
\nTo write the test, you need two pieces of information specific to your application:
\n   a) Java package of the Android app you want to run
\n   b) Activity name for the Android activity you want to launch your package<\/p>\n
You can get this information by running the following command<\/p>\n
ANDROID_HOME\\sdk\\build-tools\\android-4.4.2>aapt dump badging path_to_apk_file<\/pre>\n
\"aapt_pkg_activity\"<\/a><\/p>\n
Another approach is using the AndroidManifest.xml<\/a> which is present in the root directory of all Android applications and has the information we need. You can use Android Studio to view the AndroidManifest.xml file. Go to Build\/Analyze APK and select your apk. Then you can see the content of the AndroidManifset file.<\/p>\n
 \r\npackage=\"uk.co.aifactory.chessfree\" and \r\nandroid:name=\".ChessFreeActivity\" \r\n<\/pre>\n
3. Write the test<\/strong>
\nCreate a test script (android_chess.py) in $Directory_Of_My_Choice based on the snippet below. Pay particular attention to the setup() method.<\/p>\n
\r\n\"\"\"\r\nQxf2: Example script to run one test against the Chess Free app using Appium\r\nThe test will:\r\n- launch the app\r\n- click the 'PLAY!' button\r\n\"\"\"\r\n \r\nimport os\r\nimport unittest\r\nfrom appium import webdriver\r\nfrom time import sleep\r\n \r\nclass ChessAndroidTests(unittest.TestCase):\r\n    \"Class to run tests against the Chess Free 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'] = '8.0'\r\n        desired_caps['deviceName'] = 'Pixel'\r\n        # Returns abs path relative to this file and not cwd\r\n        desired_caps['app'] = os.path.abspath(os.path.join(os.path.dirname(__file__),'apps\/Chess Free.apk'))\r\n        desired_caps['appPackage'] = 'uk.co.aifactory.chessfree'\r\n        desired_caps['appActivity'] = '.ChessFreeActivity'\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_single_player_mode(self):\r\n        \"Test the Chess app launches correctly and click on Play button\"\r\n        element = self.driver.find_element_by_id(\"uk.co.aifactory.chessfree:id\/ButtonPlay\")\r\n        element.click()\r\n        sleep(5)\r\n \r\n#---START OF SCRIPT\r\nif __name__ == '__main__':\r\n    suite = unittest.TestLoader().loadTestsFromTestCase(ChessAndroidTests)\r\n    unittest.TextTestRunner(verbosity=2).run(suite)\r\n<\/pre>\n
4. Run the test <\/strong>
\nRun the script android_chess.py. The chess application is launched in the test emulator
\n\"Run_Chess_App\"<\/a>
\n5. Check the result<\/strong>
\n\"appium_test_run\"<\/a><\/p>\n
Celebrate a little – you just upgraded your skills by a little bit in a very short span of time! <\/p>\n
There you have it! You have just run your first mobile automated test with Appium and Python. If you are looking for Python based mobile automation framework, check out our open-sourced GUI and API automation framework based on the page object model<\/a>. Happy exploring from Qxf2 Services<\/a>!<\/p>\n
P.S.:<\/strong> As a chess fanatic<\/del>, I think it is a crime to test chess applications in an automated fashion. I sincerely believe infinite manual testing is the only correct way to test chess applications \ud83d\ude09<\/p>\n
P.P.S:<\/strong> We were pleasantly surprised by positive reaction we got to our last tutorial on mobile application testing with Selendroid. Please chime in on the direction you want our future blog posts to go. We will try our best to keep churning out useful posts for testers.<\/p>\n
\n
Hire QA consultants from Qxf2<\/h2>\n
This is an extremely old article but as you can see, Qxf2 was an early adopter of Appium. Not only did we work with Appium, we shared our learnings with the QA community as well. This has been our culture and over the years we have improved and stayed in touch with the rapid changes in the software space. In fact, we have innovated in the QA services domain too. Qxf2 offer several top-notch, unique testing services aimed towards startups<\/a> that most folks are not aware of. So, if you are working at a startup or on an early-stage product, browse our services and get in touch. After all, every team benefits from having one good technical tester!<\/p>\n","protected":false},"excerpt":{"rendered":"
Problem: There is a perception among testers that getting started with mobile automation is hard. Why this post? I strongly believe that a tester must have a wide range of skills. You do not need to be an expert in all of them, but it is extremely important to have contemplated a spectrum of concepts and explored a variety of […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[48,50,38,47,71,18],"tags":[],"class_list":["post-636","post","type-post","status-publish","format-standard","hentry","category-android","category-appium","category-automation","category-mobile","category-mobile-automation","category-python"],"_links":{"self":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/636","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/comments?post=636"}],"version-history":[{"count":38,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/636\/revisions"}],"predecessor-version":[{"id":22915,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/636\/revisions\/22915"}],"wp:attachment":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/media?parent=636"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/categories?post=636"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/tags?post=636"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}