I ve followed more or less the same principle with 3 projects:
1. actual project
2. local test project with minimal dependencies on andorid.jar
3. tests running on emulator with instrumentation
I still struggle to find a good technic where my test code takes much
more time to write then my actual code. I keep stumbling across issues
with classloading and so forth.
Have you followed this by any chance:
https://sites.google.com/site/androiddevtesting/
Mockito is very nice but did not really manage to get it fully
working. Kevin has though. I tend to mock the object myself but that
bloats the code tremendously.
./C
2009/12/8 Jan Berkel <
jan.b...@gmail.com>:
> --
>
> You received this message because you are subscribed to the Google Groups
> "LondOnAndroid" group.
> To post to this group, send email to
london...@googlegroups.com.
> To unsubscribe from this group, send email to
>
londonandroi...@googlegroups.com.
> For more options, visit this group at
>
http://groups.google.com/group/londonandroid?hl=en.
>
--
Carl-Gustaf Harroch
Sent from Bracknell, Eng, United Kingdom