Testing Esitmates for testing mobile applications
Does anyone have any good suggestions or rules of thumb when creating testing estimates for Mobile applications.
We are creating an application for Blackberry devices and while we are struggling with the huge number of variants that need to be covered (os, device model, carrier etc.)I was hoping someone might have some good suggestions on how to create estimates and properly resource a QA team to deal with Mobile applications (a point to any good resource material would be great).
Re: Testing Esitmates for testing mobile applications
Rule of thumb I use is about ~3 times the resource requirement for the complexity of desktop app. I have discussed the reasons here. This is purely based on my own experiences, and is likely to vary in your case. The experience of the testers in terms of the hardware, firmware, communications, and application domain will play a big part. Sorry but I don't have any reference material on this. Another thread containing uselful experiences is here.
To do the estimate, I would start by quantifying the number of variables and combinations you are dealing with. Having done that you can try testing some of the individual combinations, see how long it takes, and work from there.
It's would be a good exercise to browse all of the other threads in this forum for other peoples experiences, particularly with regards to potential pit falls, of which there are many.