Testing and QA
User cases are key to preparation during the final phase before app submission.
Be sure to test everything on the emulator and actual device you support. There have been instances of differences between environments including response time, screen display and functionality.
The emulator lacks real time limitations like internet connection testing for 3G versus EDGE.
When we began, the general public didn’t have access to automated functional testing.
Because of that, one of our developers created his own, UISpec, which is currently available as an open source component [www.iphonetesting.com It writes scripts around your testing keys].
Another important detail when testing these apps on the phone device, is that it has to be done from a publicly accessible server, as most corporations won’t let an iphone connect through the firewall.
Figure out early in the process for an alternate solution before developing and testing.
Remember that iPhone guidelines address specifics to iPhone and not iTouch, so take into consideration not to force capabilities to work on new OSs.
As a developer you need to think about features, so check on which device to see if you can handle, such as camera version, phone version, GPS usage, photos for the device etc.
You will learn some lessons along the way during the guideline and review process that will refine your product development, testing and product definition, and overall user experience.
Remember too that Apple’s ad hoc distribution allows for up to 100 people to “beta test" your app before you launch it publicly.
We’d recommend you take advantage of that to gain feedback and test the process.
You also receive up to 50 promo coupons for promo when it does go live on iTunes as part of the developer kit.
Testing and QA:
User cases are key to preparation during the final phase before app submission.
Be sure to test everything on the emulator and actual device you support. There have been instances of differences between environments including response time, screen display and functionality.
The emulator lacks real time limitations like internet connection testing for 3G versus EDGE.
When we began, the general public didn’t have access to automated functional testing.
As a result, one of our developers created his own, UISpec, which is currently available as an open source component [It writes scripts around your testing keys].
Another important detail when testing these apps on the phone device, is that it has to be done from a publicly accessible server, as most corporations won’t let an iphone connect through the firewall.
Figure out early in the process for an alternate solution before developing and testing.
Remember that iPhone guidelines address specifics to iPhone and not iTouch, so take into consideration not to force capabilities to work on new OSs.
As a developer you need to think about features, so check on which device to see if you can handle, such as camera version, phone version, GPS usage, photos for the device etc.
You will learn some lessons along the way during the guideline and review process that will refine your product development, testing and product definition, and overall user experience.
Remember too that Apple’s ad hoc distribution allows for up to 100 people to “beta test" your app before you launch it publicly.
We’d recommend you take advantage of that to gain feedback and test the process.
You also receive up to 50 promo coupons for promo when it does go live on iTunes as part of the developer kit.
NB: This How To series is authored by Robyn Grassanovits, Amy Dillon, Brian Knorr, Dr Maher Ali, Shannon Mihalakos and Carmen Velazquez of TripCase - an iPhone app to handle trip and itinerary management by Sabre.