| || |
Article: Configuration Testing on Mobile Devices
Last edited by yagsy; 04-12-2013 at 01:32 PM.
Great read! I've spent years working on projects spanning wide varieties of firmware/hardware combinations and can say that this sort of testing is definitely the trickiest to plan. Something I didn't catch in the article but recommend is to have a good understanding of the device/firmware spread in your market so that you can tailor your tests accordingly. It helps to have a standard batch of tests to run on all combinations possible, but in the interest of time you're better off putting more time into the sets that give the highest value for your testing. For example, there is more fragmentation on Android than on iOS, making mobile Apple development easier to predict with regards to display and functional quality. With Android, you could run a full pass of your standard checks on a certain number of "reference devices" and run cursory passes on the next batch of phones and tablets, in priority order.
Being able to automate certain tests (loading builds, running core functions, and recording video/screenshots to proof) or use an emulator as a first sweep are both good ways of setting your expecations.
Tags for this Thread