Skip to main content

Executing appium tests on android mobile app


Back to Appium Tutorial Index

Having learned how to execute appium tests on android mobile web now is the time to learn how appium tests can be executed on mobile app. Lets begin with installing app on emulator or device -

Installing app on emulator/device: Following are the steps to install app on emulator or device on various operating systems -


Windows:
  1. Start the console (Windows XP), Run -> type cmd, and move to the platform-tools folder of SDK directory.
  2. Paste the APK file in the 'android-sdk\tools' or 'platform-tools' folder.
  3. Then type the following command.
  4. adb install [.apk path]
  5. Example:
  6. adb install C:\Users\Name\MyProject\build\Jorgesys.apk
Linux:
  1. Copy the apk file to platform-tools in android-sdk linux folder.
  2. Open Terminal and navigate to platform-tools folder in android-sdk.
  3. Then Execute this command -
  4. ./adb install FileName.apk
  5. If the operation is successful (the result is displayed on the screen), then you will find your file in the launcher of your emulator.
Mac:
PATH=$PATH:~/Library/Android/sdk/platform-tools
Example : PATH=$PATH:/users/jorgesys/eclipse/android-sdk-mac_64/tools
Then run adb.
Mac:
1.Run the emulator,
2.then copy your .apk file and paste into /Users/your_system_username/Library/Android/sdk/platform-tools,
2.1. if you are not able to find sdk path in your mac system, do the following steps,Open finder->select Go option on top menu -> select Go to Folder option -> it will popup a window with a textfield: /Users/your_system_username/Library/Android/sdk/ -> now open platform-tools folder and paste your copied .apk file,
  1. Now open terminal and type the following: cd Library/Android/sdk/platform-tools
  2. execute the following in your terminal: ./adb install yourapkfilename.apk
4.1. if you get the following error message: error: no devices found - waiting for device - follow the step 5.
  1. Run your emulator from Android Studio, once emulator active then repeat step 4, you will see the success message on your terminal.


Analyzing app element locators -
You can use uiautomatorviewer to identify app elements and use them in tests


Finding app package and app activity - 
You need to know app package and app activity to be able to run test on mobile app.


  • If app is already installed on device/emulator then you can find name of app package and app activity from catlog, start -
adb catlog
Launch app on emulator/device
Find the appPackage and appActivity from cat log, for ex following are the appPackage and appActivity for calculator app on my android emulator -





  • You can also find app package and app activity from within appium app. Click android icon on appium app > select App Path checkbox > Choose apk file. After a while you will see Package and Launch Activity (app activity) on Android Settings window -


Screen Shot 2016-05-31 at 13.28.32.png


  • You can also use an app called apkinfo to find out app package and app activity for an app installed on device

Example app test -




And this test can be executed from testng.xml file.

Popular posts from this blog

Distributed Load Testing with JMeter

Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

XPath and single quotes

I had tough time dealing with XPath and single quote. Though W3C recommends using ' to escape it but I never got it working, let me know if any of you get through. Came across this blog and found that “concat” could be used in this situation. So original XPath expression is – //meta[@name=’DESCRIPTION’][@content=’Tester’s Test’] This is some thing which certainly fails as single quote in “Tester’s” marks it at end of string and then XPath blows up, next trial was – //meta[@name=’DESCRIPTION’][@content=’Tester''s Test’] This does not work despite w3c recommendation! And then I used concat function and split the string as – concat(‘Tester’,”’”,’s Test’) NOTICE that single quote is kept in double quote while other characters are kept in single quotes. So XPath looks as – //meta[@name=’DESCRIPTION’][@content=concat(‘Tester’,”’”,’s Test’)] And this works charm.