This is the 20th blog in our 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 in the 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 the 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 Bitbar Testing.
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.
Many of you have switched to Android Studio already or if not are at least planning to migrate into this new development environment at some point. Android Studio has advanced to version 126.96.36.199 and everything seems to work smoother than ever before – and this also makes testing easier and access to real devices through plugins a great option.
Regardless if you are using Android Studio (where Gradle is the default build system) you may use Gradle also with other development tools as well. Here are the basic steps and instructions of how to use our Gradle plugin to build an instant and seamless bridge between your development environment and our devices at Bitbar Testing.