This is the third of a four part series on Android Unit Testing. In
the last two articles I discussed the general principles of having
and the way to run Android tests on JVM making them
part will show how to make your Android code less heavily
coupled. This is a preparation step to ensure that your tests are
isolated from each other.
This is a companion discussion topic for the original entry at https://developer.okta.com/blog/2015/04/14/android-unit-testing-part-3