On Mon, Jan 18, 2010 at 3:54 PM, Dianne Hackborn <[email protected]> wrote: > There is absolutely no need for you to turn that into a matrix and test > every combination. Do you work on 480x854 screens? Great, you have that > covered regardless of the platform.
But not hardware, different phones behave differently sometimes, even with the same resolution. > (1) Platform versions: 1.5, 1.6, 2.x (pretty soon just 2.1; 2.0 and 2.0.1 > are on the way out). Low as they are, my stats show 2.0 and 2.0.1 are ramping up, not down. > Most important are the lowest and highest versions to > be supported; intermediate ones can be given a cursory sanity check. Cursory sanity checks still require firing up yet another emulator. This takes more than two minutes even on a smoking fast i7 machine like mine. > So you should be able to fairly easily get away with testing: 1.5 HVGA, 2.1 > HVGA, 2.1 480x854, and add 1.6 QVGA if you want to support small screens. > Spot check other variations as desired (and knowing what your app does that > it might get into trouble with). Even when giving it just some half-hearted effort like you suggest, that's still a minimum of 3-4 emulators. That's still a ton of testing time, especially for a non-trivial app with lots of different execution paths. -- Greg Donald destiney.com | gregdonald.com
-- 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
