This is the 20th blog in our 37 Things You Should Know About Appium blog series and this time we’ll take a look on how to bridge the gap between Android Studio, Gradle and Appium tests running on a real device on cloud. As you know, Appium client-side execution is slightly different compared to how other test automation frameworks are used and you typically just upload your APK (or IPA for iOS) first, then start your test from localhost and once test is finalized you’ll (or your scripts) pull back the results for local inspection. Now, let’s look on how to get your Appium tests up and running — when built with Gradle.
As it seems that Google is officially ending the support of Eclipse-based Android Development Toolkit (ADT), we’ve prepared everything for you in Android Studio and our Gradle-based plugin is readily available to get your tests seamlessly running from Android Studio (instead of using our old Eclipse-plugin) to Testdroid Cloud.
According to that blog, Google will end their development and official support for ADT at the end of this year and both Eclipse ADT and Android Ant build system are affected.
Google recently released a long-awaited new version of Espresso (known as v2.0 now). Even the first version sparked some noticeable interest among test automation community, it seems that the second version is a great improvement and should be definitely checked out by everyone who uses Espresso as their test automation framework.
We’ve been providing support for the first version of Espresso about a year now – and now officially for v2.0. Check it out – it’s great promising framework for your app testing! And it’s FAAAAST!