Nando Scheidecker wrote: > Every time I have to bring the emulator (even on a fast Linux machine) > to test an app is quite painful.
Note that you can keep your emulator running for most tests. The main time you really need to stop and restart the emulator is if you are testing things that happen at boot time. > What would you suggest to speed up the development of an app w/o usinf > the emulator? You can experiment with the android-x86.org project and use it on a spare PC or a VirtualBox image. This allows you to avoid the ARM->x86 opcode conversion. On the other hand, it limits you to Android 1.6 at present. > I thought that JUnit for the logical parts would help. > > Basically, I want to be able to test the app within Eclipse as much as I > can before testing on the emulator. You are welcome to package Android-independent code into its own project for testing, perhaps generating a JAR that your Android project then uses. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Consulting: http://commonsware.com/consulting -- 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
