02-09-2012 11:43 AM
I am preparing my first HTML5 app for release.
I've compiled it using Ripple and would now like to test the source code.
My app will only run in OS6 and OS7.
In order to fully test it, I planned to run it against an OS6 simulator, and OS7 simulator, and OS6 device and an OS7 device. However, it looks like there are about a dozen or more permutations of the version 6 OS simulators.
In order to clear my app for OS6, do I need to test against each and every version?
Can anyone give me some guidcance on this?
02-09-2012 04:48 PM
You need to test on real devices. It's 10 times more important than testing on simulators.
Here's a start:
- No network
- Just WiFi
- Just Cellular
- WiFi & Cellular
- OS 7.0 Full touch screen (9810 and 9850)
- OS 7.0 Touch screen and keyboard (9900)
- OS 6.0 Low res (320x240) - Curves
- OS 6.0 High res - (480x360) - Bold 9780 or 9700 running 6, or a newer Curve
- OS 6.0 Touch (Torch 9800)
02-13-2012 09:33 PM
Found one alternative to purchasing the phones.
Companies offer just about all BB phones available through the web for testing.
You upload your program and test on a real blackberry that you control through a web browser.
Have not figured out how to actually install my program on one of their phones though. Posting another message about that.
02-20-2012 11:14 PM - edited 02-20-2012 11:15 PM
I have been using the Perfecto Mobile service for a few weeks and thought I'd drop a line here to let anyone who may be interested know a few things. I think Perfecto works best AFTER you have done all your testing on a physical blackberry that you have in front of you. The reason is I encountered strange behavior when testing my app on Perfecto- behavior that they could not explain and I did not expect. It wasn't until I actually had my app loaded on a physical device in front of me that I could begin to figure out what was going on. After it's up and running on a physical device, that's when I'd recommend using perfecto- just for polishing, double and triple checks. Not as primary testing resource.