Develop a Quality Assurance Test Plan

[multidynamic]

Matthew Adler created an issue 2014-12-10
For client black-box style testing some sort of test plan should be conducted. This ticket is about creating such a testplan. To reduce bias, the final approval should be conducted by a person who did not develop the application.

Google has a good starting spot here: http://developer.android.com/distribute/essentials/quality/core.html
The app should be tested on a Android representational device, such as a Nexus. Google vets the nexus and it is likely to be the closest to what Google sees as a good representation of Android. Issues here are unlikely handset issues.

After running a successful test plan I recommend testing on tablet, popular devices, and a device with with android of the lowest supported version.

Google has advised test-plans for tablet testing: http://developer.android.com/distribute/essentials/quality/tablets.html

But since tablets are not as popular as handsets I think less focus is acceptable here. Do initial UI testing on the emulator and final pass through with a physical device.
To alleviate costs of procurement, DeviceAnywhere can be used instead.

❌ A major enhancement

Matthew Adler REPORTER 2014-12-10
I have a LG Nexus 5, a couple LG Optimas with cynogen Gingerbread and stock Eclair installed, and the original Moto Driod with stock Fryo.

eosrei 2014-12-10
I've got a Sony Xperia T with CyanogenMod 11 (KitKat 4.4) and a Nexus 10 with Android 5.