So we can say that this: https://sites.google.com/site/androiddevtesting/notepadsample is a real unit test (using the JVM) and the one on the android developers site is a integration test (DVM).
On Nov 9, 11:21 pm, Frank Weiss <[email protected]> wrote: > You've raised a good question. It's correct to to say that a unit test does > not involve all the classes of an application. Unit tests are also supposed > to run very quickly. We also usually don't include the GUI in unit tests. > Neither external web services. > > In Android, though, we have a bit of a problem. To really run even by the > book unit tests, we'd have to either run them on the JVM or the DVM. In the > first case, we would be using .class files, in the latter case, .dex files. > But I don't know if we have DVM for anything but the emulator or the device. > And the emulator's DVM tends to run slow. Hmmm. > > I would tend to agree that what is called unit testing in the Android SDK is > a bit different than the norm. I'd like to hear what others have to say. -- 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
