Revision 2.0 of the book was published on Januand has been fully updated to cover the changes introduced in the Android Studio 1.x release and the Android 5 SDK. The revision of your copy of the book can be found in the copyright page at the start of the book. Our build.Android Studio Development Essentials was published on July 21, 2014. That’s it! We can now add our test dependencies and get to writing tests. The only step we need to take is to select the correct Build Variant Test Artifact: release is no longer valid for Android Studio 1.2. The unit testing how-to post that accompanied the Android Studio 1.1. I’ll then go back and explain how to transition away from the more complicated approach I described in January. Today I’d like to walk through the greatly simplified steps to set up unit testing in Android Studio. While the Nerds here at the Ranch are quite surprised that nary a word was mentioned in the release notice for v1.2, unit testing support is here to stay. Last week with the beta release of 1.2, that setting is no longer experimental.

It included an experimental setting to enable unit testing. The groundwork was introduced in Android Studio 1.1, which was released back in February.

Android Studio 1.2, which is currently in beta, removes any need for third-party workarounds or custom hacks to Robolectric. Today, all of those workarounds are completely unnecessary, thanks to the Android Tools team. We knew that better testing tools were in the works-the measures I described in my previous post were just a stopgap.

If you were committed enough to get through the whole post, you’ll remember how tedious the setup was. I wrote about setting up unit testing in Android Studio back in January. We’ve been monitoring the state of testing in the Android world for some time now, waiting for the day when testing would be fully baked into the Android development cycle.

How to update android studio 1.2