Thanks for the response. I am aware of the instrumentation mechanism to run tests, however I have been unable to determine how to use it in conjunction with the debugger in eclipse, thus it is essentially useless to me.
On Apr 5, 11:10 pm, Andrew Stadler <stad...@gmail.com> wrote: > It's actually quite useful and doable to write "pure" unit tests > within the InstrumentationTestRunner framework. > > For a working example, please take a look at ApiDemos, in the tests/ > directory, and look for classes that extend the "TestCase" class. > > Benefits of doing it this way: > > 1. Although you can restrict yourself to pure JUnit style tests if > you want, you can also write a mix of tests, ranging from purely unit > (extending TestCase and AndroidTestCase) to almost totally functional > (e.g. extending ActivityInstrumentationTestCase) and group them > together as a test suite. > > 2. Although it doesn't work in the published SDK, quite soon you will > in fact be able to run these tests directly from Eclipse. In other > words, because this is the supported mechanism, you'll benefit from > upcoming improvements & tools. > > Hope this helps. > > --Andy > > On Fri, Mar 27, 2009 at 10:15 PM, gudujarlson <gudujarl...@gmail.com> wrote: > > > I discovered that at least some of JUnit exists on the emulator. In > > particular TestCase and Assert exist. However, TestRunner does not > > appear to exist. I find it odd that only parts of JUnit are present. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
