In this chapter, we looked at several options to test Android apps and libraries. We started out with simple unit tests, and then looked at more Android-specific testing with Robolectric. Then we covered functional tests and getting started with Espresso. Finally, we looked at enabling test coverage reports to see where the test suite needs to be improved. Now that you know how to run the entire test suite with Gradle and Android Studio, and you can generate coverage reports, there are no excuses not to write tests. In Chapter 8, Setting Up Continuous Integration, we will look at more ways to automate tests with continuous integration tools.

The next chapter covers one of the most important aspects of customizing the build process: creating custom tasks and plugins. The chapter also includes a short introduction to Groovy. This will not only help when creating tasks and plugins, but will also make it easier to understand how Gradle works.