One of my biggest aggravations with Android development is the length of time it takes to run simple unit tests on a device or emulator. The compile/package/deploy/test cycle just takes too long to run on a regular basis, and so I tend to drift away from good unit testing practice, and towards more integration or acceptance test process. This means that I frequently end up navigating the application to the area that I actually want to test, slowing down the development process significantly.

This is Part 3 in a series focusing on building Android apps using Maven and Continuous Integration. My previous post looked at setting up a local Jenkins server.

This is Part 2 in a series focusing on building Android apps using Maven and Continuous Integration. My previous post looked at setting up Maven and overcoming the Android dependency issues.

For a while I have been building all my Android projects locally, using the standard Ant build scripts inside IntelliJ.
Recently I decided to try to step up my build process and use Continuous Integration, a dependency management system, and JVM-based unit tests. This series of articles provides some insight into the method used, and the various failures I encountered on the way.