Yes, the android classes mocked by mockito should work, except for final classes (Bundle) or final methods. But as you said, testing a class that inherits from an Android class (Activity, Service, BroadcastReceiver) will not work since you can't mock them and you aren't running on emulator. But everything else should work. And yeah you can use a robolectric gradle plugin and just make your tests not use robolectric at all and you won't have to reinvent the wheel.
Jürgen On Thursday, June 12, 2014 7:54:21 AM UTC-5, Per Christian Henden wrote: > > Yes, you don't get the real Android classes with Mockito, you get mock > implementations, which is a nice solution for unit tests. > Basically you specify through Mockito how each Android class that your > test code depends on should behave. Typically this means instrumenting the > Android classes to return some static dummy values so that your test code > can do its work. It's not a good fit if you are testing things related to > the GUI or Activity lifecycle. > > Thanks for pointing out that the workarounds suggested for Android > Studio/IDEA for Robolectric-gradle applies to this case too :) > > kl. 14:16:14 UTC+2 torsdag 12. juni 2014 skrev Jürgen Cruz følgende: >> >> As far as I know, even with mockito, you can't run android clases in JVM. >> That is why robolectric had to make a runner that intercepts the bytecode >> and a lot more magic things. >> >> But you are having the same problem as robolectric users. The best I have >> been able to do was to manually modify the .iml files to include the source >> and the libraries folder to include the dependencies >> > -- 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.
