Testing on the Client

UnitTesting?

Android has implemented its own version of the jUnit 3 library. We use this to do unit testing. The Android API has extra classes for testing Services, Activities and other key parts of the Android application layer.

Mocking

We use a mocking framework. But mostly for doing stub classes easily.
But be aware that there is a huge difference between stubbing and mocking, and the two different testing philosophies behind doing state or behavior tests.
 Mocks Aren't Stubs

Frameworks

There are a few different mocking frameworks for java of which I have been considering  EasyMock and  mockito. But when testing out mockito i ran into a problem.

Mockito on Android

 http://code.google.com/p/mockito/issues/detail?id=57#c14
It seems that the Dalvik VM doesn't support the library correctly, and the developers of the mockito are not going to address this issue.

The reason why I was considering mockito in the first place is for it's ability to do partial mocks.

EasyMock on Android

It runs flawlessly this far, but it cannot do partial mocks. Which isn't advocated for new projects anyway. The general message is that one should rearrange responsibilities of the classes if it's so cluttered that you have to do partial mocks in the first place.  http://mockito.googlecode.com/svn/branches/1.8.0/javadoc/org/mockito/Mockito.html#16

EasyMock only does mocks of interfaces.