Espresso is unable to run it's own unit tests about android-test-kit HOT 7 CLOSED

Workaround:
adb shell setprop dalvik.vm.dexopt-flags v=n,o=v
adb shell stop installd
adb shell start installd

reinstall the packages / run the test and it should be fine.

Background:

When you execute am instrument ... the classpath from the test apk and app apk 
are combined. If duplicate class definitions exist (even if they are identical) 
you'll get this exception.

The above set of adb commands disable the optimization that causes it to be a 
problem. 

Full fix is to muck the build scripts to prevent duplicate class elements 
appearing in both the test apk and the app apk.

@Stephan - do you think this falls under the issues you're tackling with 
gradlefication?

Issue 10 has been merged into this issue.

If you exclude Guava from the test APK, it seems to solve this particular 
problem, but some of the tests seem to fail. See attached patch.

[INFO]   Tests run: 165,  Failures: 4,  Errors: 2

I ran it with the patch and it finally worked but my results on a Nexus 5 are a 
little different:
 Tests run: 165,  Failures: 4,  Errors: 1

Please try again with the new release. We fixed the duplicate dependencies 
issue.

Thanks. It looks like this commit fixed the issue:

https://code.google.com/p/android-test-kit/source/detail?r=aaf0047dfd8543997d365
2b9d75a63ece95f18df#