In an earlier post we explored using Selendroid and Python. On the eve of Christmas 2013, Selenium officially retired their own AndroidDriver and iPhoneDriver in favour of Selendroid, iosdriver and Appium. The tools your test team uses to solve the specific and unique problems can greatly vary. NOTE: In this post we are concentrating only on the “getting started” phase. 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. At Qxf2 Services, we have decided to tackle the problem head-on. Testers are reluctant to get started with mobile testing – probably because they think getting started involves a lot of time and effort. In this regard, I began noticing that mobile testing has become somewhat of a niche among testers.

The more options you are aware of, the better your context-specific choice is going to be.

The context under which you test will inform you of the specific choice of testing methodology and test tools to choose. 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. I strongly believe that a tester must have a wide range of skills. Problem: There is a perception among testers that getting started with mobile automation is hard.

Android appium on mac emulator