Please post your Web Driver questions in official Web Driver forum

Monday, June 20, 2016

Executing appium tests on iOS mobile web

Back to Appium Tutorial Index  

To be able to work with ios simulator we would need -
  • Appium app to launch appium server and analyze application elements
  • xCode to launch various simulators to run tests on emulator / or real devices
Let’s begin with Appium app installation on mac -


Appium app provides ready to run version of appium server. Install appium client and start appium server as described in following steps -
Install latest Appium client for ios from - http://appium.io/downloads.html (You may have issues downloading this file from chrome, FF seems to work without issues)
Once download is over then Control-click appium.dmg > open with > DiskImageMounter.app
DMG is a apple disk image. The disk image will be mounted.


Screen Shot 2016-05-31 at 12.31.31.png


Then look for the mounted disk image in your finder (cmd + space), It will appear there. Right click and open. You should also drag it to Applications folder so that you can search it in finder (command + tab) in future.
Screen Shot 2016-05-31 at 12.41.38.png


After app verification you will see a warning > Click Open


Screen Shot 2016-05-31 at 12.44.57.png


You will see a warning for Appium authorization to run iOS simulator > Select Yes
Screen Shot 2016-05-31 at 12.50.06.png


Click the Launch button to launch appium inspector. If everything goes ok then you should see Welcome message


Screen Shot 2016-05-31 at 13.12.25.png


Once you launch an app on emulator then you can click on magnifying glass (appium inspector) to verify application elements.


By default appium app runs the bundled version of appium. If you are running a newest version of appium from source then select it under Preference > Use External Appium Package checkbox


Screen Shot 2016-05-31 at 15.52.57.png


Now we need to install Xcode for OSx
Install Xcode 6.0.0 (or higher) from the App Store. From wikipedia - Xcode is an integrated development environment (IDE) containing a suite of software development tools developed by Apple for developing software for OS X, iOS, WatchOS and tvOS. You could refer Xcode beginners guide to get a gist of Xcode.


If you use xCode version lower than 6.0.0 then you would encounter following error when running test -


org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: Tried to use an iOS simulator with xcode version 5.1.1 but only Xcode version 6.0.0 and up are supported (WARNING: The server did not provide any stacktrace information)


Refer the apple simulator user guide to get very detailed info on simulator. You may be specifically interested in how to change simulated device and OS version to be able to test app/web on different versions of device and OS.


Assuming that Xcode is installed, you can launch ios simulator as following -


Xcode > Open Developer Tool > iOS Simulator
Screen Shot 2016-06-01 at 14.10.24.png


To Download other versions of iOS simulator, select Xcode > Preferences > Downloads and select the ios Simulator you want to download -
Screen Shot 2016-06-01 at 14.13.16.png


You can also change the type of simulator launched, for example if iOS simulator launches iPad and you want to use iPhone then you can change the device hardware from top menu as following -


Screen Shot 2016-06-02 at 12.26.48.png

Now head over to testng.xml to execute ios web test :)

Wednesday, June 8, 2016

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.

Sunday, May 29, 2016

Where is my default Test Data

Importance of test data can not be emphasized enough whether we are writing automated or manual tests. With automated test we often deal with data objects. Data object is an object which encapsulates properties of data dealing with object. For example username and password could be encapsulated in to Credential object and passed on to required test methods.

But many a times we require default test data which can be used to facilitate system under test reach certain stage. How do we provide such default test data so that it is readily available for use? One way to deal with this is to use constructor on data object class which would initialize the data object with default data. In the following example TeamAttributes data object is initialized with default values -


Screenshot from 2016-04-20 09:59:30.png

Of course default values can also be read from a property file instead of being hardcoded as above :-)

And now if any of your test want to use default data then they can just instantiate data object class as-

Screenshot from 2016-04-20 10:03:49.png

What do you think of this approach of providing default test data? How do you handle default test data?

Where is my defect ID?

Don't you feel ecstatic when your automated tests find bug? After all tests finding bugs give us a sense of accomplishment, is not it? And this is followed by usual cycle of defect reporting, retesting and hopefully closure of defect.
But at times defects are deferred to next or future releases. Which causes test method to fail for subsequent releases. And if you are dealing with a test suite having 100s of tests then it may become difficult to remember if there was a defect reported for a failing test? How do you deal with such situation.
How about adding defect-id to @description tag of TestNG test. Hence it is reported on automated test report and we would know if defect exists for a failing test -


Screenshot from 2016-04-06 16:14:02.png

How do you track defect-id of a failing test?
Fork me on GitHub