FYI, my problem ended up being a product of compiling the dagger 2 dagger-compile artifact into my application. You can find the details here, https://github.com/google/dagger/issues/271
If you determine you've having the same issue I've updated the README for gradle users here, https://github.com/kkovach/dagger/tree/update-install-gradle - Kevin On Wednesday, December 2, 2015 at 12:29:59 PM UTC-5, Mariusz S wrote: > > Just to let you know - I am having the same problem for some time and > still looking for a solution. > > W dniu poniedziałek, 16 listopada 2015 21:19:36 UTC+1 użytkownik Kevin > Kovach napisał: >> >> I have a library project that I've written tests for. >> >> - My tests are in src/androidTest/java/ >> - I've set testInstrumentationRunner >> 'android.support.test.runner.AndroidJUnitRunner' >> - The test classes are @RunWith(AndroidJUnit4.class) >> - Individual tests are annotated with @Test >> >> I can execute a ./gradlew connectedCheck and the tests run well on a >> device with KitKat, but when I try to run the same tests the same way on a >> device with Lollipop I get... >> >> 15:02:15.784 [WARN] [org.gradle.api.Task] Tests on XT1095 - 5.1 failed: >> Instrumentation run failed due to 'java.lang.NoClassDefFoundError' >> 15:02:16.011 [WARN] [org.gradle.api.Task] >> com.android.builder.testing.ConnectedDevice > No tests found.[XT1095 - >> 5.1] FAILED >> 15:02:16.011 [WARN] [org.gradle.api.Task] No tests found. This usually >> means that your test classes are not in the form that your test runner >> expects (e.g. don't inherit from TestCase or lack @Test annotations). >> >> This is confusing and I'm at a loss as to what I'm missing or doing >> incorrectly. Has anyone else experienced this difference between versions? >> Please let me know what other information I can provide to try and figure >> this out. Thanks. >> >> - Kevin >> > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
