Skip to main content

Appium Tutorials

Why another doc on Appium?

My journey towards learning appium began with great excitement but road was quite bumpy too. Undoubtly has tons of information but it is enervating to find exact piece of information one is looking for m-site or app automation. Scanning through appium docs, stack overflow and tons of other online doc, one would be eventually able to find how to launch browser mobile browser on m-site. It took me three days to be able to launch website on chrome browser on android phone. But the struggle was worth it :-) And this was the main motivation behind writing this doc. A step by step description of how Appium could be set up to run tests on mobile site or app on a real mobile device or emulator. So lets begin learning Appium.

Appium Video Tutorials

Appium Training Topic
Appium Training Video

Appium and Android Web test run

  • Why Appium? > WebDriver for mobile devices

 - Appium server written in node js exposes Rest API to interact with AUT
 - Start Appium server
 - Inspect element
 - Desired Capabilities
 - Enable developer mode on Android and enable USB debugging >

adb > command line tool that lets you communicate with an emulator or android device
 - Install android debug bridge
 - adb devices

Execute Android Web test



Appium and Android mobile app test run

  • Start appium and start appium inspector
  • Desired Capabilities
    • platformName - Android
    • deviceName - L2N0219828001013 (as seen on "adb devices")
  • Saved Capability Sets
  • Start Session
  • Scan app elements using appium inspector
  • Get appPackage and appActivity using "APK info" app
    • Install "APK info" app and open app whose appPackage and appActivity are required i.e. calculator
    • Check top section of app icon
      • is app package
      • is app activity
  • testng.xml file settings for running Android app tests
  • Test details and CalculatorScreen class
  • View beautiful STF test report




Popular posts from this blog

How to write bad UI automation code (a formal guide)

You might find umpteen resources on learning to write UI automation. But rarely you find any guide on writing bad automation code. Bad automation code is not actually "bad" especially when you consider following - Bad automation code keeps you job safe. Well who can understand the code other than you. Gives you an opportunity to ask for more raise as you are the only one who can maintain the code you write Lets you keep your head up as you the geek of your company who knows that abstruse code  Now coming to writing bad automation code, here are some silver bullets - Record and Replay is the core or writing good (read bad) automation code. It has so many advantages which just out do many others. Biggest being you don't have to write any good code (read bad), tool does it for you. The way to convince decision owners in to enlightening is to let them know that record and replay does not require any special skills. Even your HR can do this.

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

Verify email confirmation using Selenium

Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can