I find that most of my problems are device or user specific issues. So to be useful, the unit tests would have to run on the actual hardware used by consumers, and would have to emulate the behavior of real users.
Years ago, when I had to write a small bit of generic java code for server side logging, reporting, and metrics, that was going to be used for lots of different purposes, we used test driven development, and I was glad for the experience. So basically, I suggest you use the right tool to ensure the right level of quality for each specific project. On Mar 11, 1:36 pm, DulcetTone <dulcett...@gmail.com> wrote: > I routinely find a disproportionate number of my bugs and crashes > reside in the code set up for the purpose of testing and evaluation of > the program rather in the function of the program itself. > > I'm sure this is a measure of my unfamiliarity with "best practices", > but I find it more beneficial to try to write crash-detection-and- > reporting code rather than explore testing. That said, I am not > inspired to look at junit.org > > tone -- 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
