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

Reply via email to