Logo
/ mobile-testing

6 iOS and Android Automation Tools for mobile testing

By DeviQA on Tue Jan 17 2017 00:00:00 GMT+0000 (Coordinated Universal Time)

Subscribe Now!

Get the latest QA news and tips from DeviQA

Various mobile testing tools have been grown recently to hold up mobile development. Because of many mobile products are being developed and Marketplace is seeing a various amount of new devices and versions testing mobile apps is essential. Let’s consider some of the best android automation testing tools and most popular ios automation testing tools.

iOS automation tools

Xamarin.UITest

The testing tool activates Automated UI Acceptance Tests written in NUnit that are run against iOS applications. It assimilates closely with Xamarin.iOS and Xamarin as well. It might be used with iOS projects. These projects must be written in Objective-C/Swift and Java. The NUnit tests can be accomplished on iOS devices. When user enters a text or tap any button this tool interacts with user interface.

Test class that is called fixture comprises the tests (as UITest is written as a method that is referred to as a test).It can contain a single test or group of tests. The fixture is in charge of any setup to make the test run and any cleanup that needs to be carried out when the test is finished.

The test fixture includes either a single test or logical complex of tests. It is liable for all the setups to make the test run and any cleanup that needs to be performed when the test finishes.

Any test must keep to the Arrange-Act-Assert pattern:

1.

Arrange – Conditions will be set up and things will be initialized. In the wake of it the test can be actioned.

2.

Act – The test will coact with the application, enter text, pushing buttons, and so on.

3.

Assert – The test views the results of the actions accomplished in the Act step to spot the regularity. For instance, when a particular error message is shown the application may verify it. You can load the tests to Xamarin Test Cloud where the tests are run on pre-selected devices. Or you can run the tests locally against a device or simulator by applying the Test Runner in Xamarin Studio.

Frank

The next iOS automation tool is Frank. Test scenarios that are written in English-like statements are used in this text and are maintained by Cucumber framework. Frank needs to be carried inside the source code and its commands are combination of Cucumber statements and JSON commands. It offers large community support, easy to understand English-like statements and expanding libraries.The ‘Cucumber Recipes’ book has a nice step-by-step recipe called Test iOS Using Frank that is able to help for new automation testers.

Saying about disadvantages, Frank is not considered as simple tool to use because it is difficult to run on devices and it has limited support for gestures like pinch and zoom etc. Additionally, in order to run Frank on real devices, it is required to make changes in the configuration files which could be a large issue in certain occasions.

iOS-driver

This ios automation testing tool gives you an opportunity to automate any native iOS, hybrid, or mobile web application. It is absolutely compatible with the Selenium and Webdriver API. Therefore the iOS automation is as simple as automation for browser.

As this tool can wholly integrate with Selenium Grid you are able to reuse your web automation infrastructure including your helper and utility classes. It can be data creation or page objects.

As one of the ios test automation tools it has the next features:

It can implement the JSON wire protocol;

You are able to apply emulators for running it;

It can be run as a regular node in a Selenium Grid;

You do not have to change the sources or jailbreak the device;

Additional apps are not compulsory.

But using simulators is the default way to use ios-driver. It offers more pliancy, and it is faster than tests on a real device.

Android automation tools

Espresso

Espresso is considered as the recent Android test automation framework that got open-sourced by Google, making it available for developers and testers to hammer out their UIs. Espresso has an API that is small, easy to learn and built on top of the Android instrumentation framework. You can rapidly write concise and trusted Android UI tests with it. It is supported on API level 8, 10, 15 and afterwards. It’s quite trusted, synchronizing with the UI thread and quick. But it also with has no support for webviews as Uiautomator.

Robotium

We already have mentioned this tool in our previous post. But it also match criterias of best Android automation tool. Let’s take a quick look. It was the most widely used Android testing framework in the early days of Android. A resemblance with Selenium in Android makes testing API quite simple. Robotium is an open source library extending of JUnit with wide range of useful methods for Android UI testing. It provides powerful and robust automatic black-box test cases for Android apps (either native or hybrid) and web testing. Robotium enables you to write function, system and acceptance automation tests.

Selendroid (Android)

Selendroid is also one of the automation tools for android testing which drives off the UI of Android native and hybrid applications (apps) and the mobile web. Selenium 2 client API is used to write tests. It has following features:

It has full compatibility with the JSON Wire Protocol Selenium 3 Ready;

Existing Emulators are started automatically;

You are able to extend it at runtime with your own extensions;

It supports hot plugging of hardware devices;

Selendroid can coact with multiple Android devices simultaneously. It can be emulators or hardware devices;

The concept is the same for automating native or hybrid apps.

Try all of the above mentioned tools and select one you like more to develop quality automation tests. Each of the above tools has pros and cons so think about your testing need: UI testing, compatibility testing, functional testing and so on and pick up the best tool for you. Keep in mind that automation test is a hard complex work which require continuous self learning and web research.