Use timber You can create a custom tree for releases so you can send logs to Crashlytics or other thing without changing any line of code.
Sometimes you need to wait before some async operations (maybe some EventBus or RXJava Observables) end before check something with tests, now Espresso can handle the idling resources but JUnit not. Using assertj-android but you use to handle async operations and tests will fail because of sync.
For JUnit 3
There are some conflicts on espresso dependencies so just include com.android.support.test.espresso:espresso-contrib:2.2 with some excludes.
Take @3x as your base image size and check: