There ’ s no disputing that anautomated quizframework is an integral part of the software development round. You utterly need automated testing to deliver quality application in a timely fashion, particularly for quickly changing peregrine apps.

To draw the greatest benefit from your software delivery, your automated tryout should be carefully planned and scheduled in such a way that they are cost-effective. For this role, the right choice of tools is critical. It ’ s also a difficult choice to make, because navigating through the vast variety of try tools available for wandering developer nowadays can be very challenging.

With this article, I ’ m here to facilitate. Below, I provide a guide for evaluating various Android UI frameworks. The creature are listed in alphabetical order.

Appium

http: //appium.io/

Appium is an open-source peregrine testing tool that supports both iOS and Android. It can be expend to essay any type of mobile app: native, web and hybrid. Appium is a cross-platform tool, meaning you can run the same test on different program. To achieve this cross-platform potentiality, Appium utilizes vendor-provided Android UI model for screen: XCTest for iOS and UIAutomator or Instrumentation for Android. It wraps these vendor frameworks into Selenium WebDriver. This allows Appium developer to compose tests in a wide variety of programme languages: Java, Objective-C, JavaScript, PHP, Ruby, Python, etc. It also get writing the Appium examination very similar to writing Selenium examination.

As WebDriver was initially created for web testing, Appium extend WebDriver with extra API method to make it more worthy for mobile mechanisation.

Here are some additional utilitarian Appium characteristic:

• You don ’ t postulate to install anything on the twist.

• You don ’ t need to recompile or change your app in any way to try it with Appium.

• Appium has a very big and active community.

• Appium come with a tool to scan and dissect an application ’ s UI components— Appium UI Inspector. Developers can also use Android Studio ’ sUI Automator Viewer.

If you ask to write tests for both iOS and Android, and you ’ re a Selenium fan, Appium would be a great choice for you.

Appium is supported by Sauce Labs for testing with aper, simulator and real devices. Sauce is also highly combat-ready in the development of Appium itself, with a act of Sauce developers contributing to the program.

Calabash

Calabash is an open-source mobile testing tool that was developed and maintain by Xamarin. It supports aboriginal and hybrid apps on both iOS and Android. The set of activity that can be perform by Calabash testing include gestures, assertions, and screenshots. Calabash is integrated with Cucumber, a try tool for Behavior-Driven Development.

Xamarin announced in 2017that it was end fighting development of Calabash. While you can still use Calabash for now, the decision to cease ontogeny makes Calabash a less-than- ideal testing solution.

Espresso

https: //developer.android.com/training/testing/espresso/index.html

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

Espresso is an Android UI Framework from Google. It ’ s a lightweight, white-box tool point towards app developers, which means to use it to its entire potential, the test developer has to be fully familiar with and have accession to app code. As a effect, Espresso tryout are very reliable and they run fast. And as Espresso has access to UI aim ’ internals, it can examine WebView, i.e. hybrid applications. Tests are indite in Java. (Duh!)

On the downside, Espresso can test only one application at a time, and doesn ’ t have admittance to device resources. However, this could be easy solved by creating combined test with UI Automator. This blog post explains how to do precisely that:http: //qathread.blogspot.com/2015/05/espresso-uiautomator-perfect-tandem.html

Sauce Labs also endorse Espresso for testing on existent devices.

UI Automator

https: //developer.android.com/training/testing/ui-automator.html

UI Automator is an Android UI framework for mobile examine developed and maintained by Google. Its key features include cross-app functional testing, the power to test multiple apps, and switch between installed and scheme apps.

UI Automator is a black-box examination instrument (i.e., a test developer doesn ’ t need to know the internal app construction and can rely wholly on visible UI elements). Not amazingly, UI Automator ’ s tests are publish in Java, Google ’ s ultimate language of choice. UI Automator consists of two set of APIs: UI Automator APIs, to manipulate the UI components of an app, and device province APIs, to access and perform operations on the twist (vary the gimmick rotation, press the rear, home or menu button, etc). It also comes with a very useful UI Automator Viewer, a GUI tool to scan and analyze the UI components currently expose on the device.

The downside of the UI Automator is that it doesn ’ t support WebView, upon which intercrossed Android apps are built. Therefore, UI Automator supports only aboriginal Android apps.

Robotium

https: //github.com/RobotiumTech/robotium

Robotium is an open seed Android UI fabric. It has been around since 2010, and by now is a real mature and stable tool. The terminal edition, 5.6.3, was released in Sept. 2016. In the last few versions, test legibility and test performance speed have been significantly improved.

Most technological blogs, tutorials, and courses refer to the character of testing utilized by Robotium as black-box testing. I would fence that it is really gray-box testing, because to write Robotium tests, you need to know the internal application construction, at least part (activities ’ names, for example).

Robotium is an propagation of the Android examination framework and, as such, it utilizes run-time binding to UI components, which create tests more robust. Robotium comes as a jar file that has to be compile with your project.

This is a fond list of the main Robotium features:

• Supports both native and hybrid application

• Can run tests on both real devices and emulators

• Supports full Android UI paraphernalia: activities, button, menus, goner, dialogs, etc.

• Supports motion

• Has some device control functions: alteration device orientation, take screenshots, unlock screen, etc.

• Robotium recorder (https: //robotium.com/) is uncommitted as a paid Android Studio and Eclipse plugin. It ’ s a great tool to get up and running with tests quickly.

• Can run as part of uninterrupted integration

• Robotium ’ s language of choice is Java.

Robotium is also indorse by Sauce Labs for screen on real device.

Conclusion

Choosing the correct Android UI framework for mobile screen for your projection is challenging. In some cases, you may postulate to use multiple tools to strike the right balance. This is why a testing grid like Sauce Labs is helpful as it back multiple testing frameworks.

Nadia Minaev is a Fixate IO Contributor and a software engineer with deep knowledge in a wide variety of modern technologies. Throughout her career she has worked for such well-known technology leaders as HP, Intel and others. Nadia founded Alkon Technologies, a software development society, and FarmGalaxy, a mobile app that colligate local farmers to their customers.