Everything should, and now must, run on the emulator or on a device. This is the only way to guarantee a program works (if only to run it on Dalvik rather than a stock JVM.) For what it's worth, that's how we run all of our tests in the Android team.
We have special support for tests, especially instrumented tests in the framework. You can refer to the samples (apidemos) to see how they're set up. On Sep 27, 2008 12:30 AM, "Shane Isbell" <[EMAIL PROTECTED]> wrote: On Sat, Sep 27, 2008 at 12:24 AM, Romain Guy <[EMAIL PROTECTED]> wrote: > > How so? Aren't you ru... Some I do and some I don't. I've got the Masa plugins (for Maven builds) setup to do both. By simply hooking a value object like ContentValues into one of my classes, it now becomes untestable as a normal unit test, as I now get a runtime exception on ContentValues initialization. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are su... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
