Quote:
Originally Posted by johnqh
Did people forget the most important thing?
#1. Test, test and test.
Have you tested on all hardware models?
If that's difficult, have you tested on all versions of the OS? (2.0, 2.1, 2.2, 2.2.1)
At least, have you tested the release build?
Personally, I had an app whose debug version ran fine but release build crashes. Fortunately Apple caught that.
Then, I had another app which worked fine on my iPhone (3.0 and then I tested in 2.2.1), but crashed on 2.1 and 2.2. Seems to be an Apple threading bug. I wished I tested on earlier OS.
|
I don't think anyone forgot that, it was just assumed that if it was "ready for release" that the testing had been completed with some level of competence
I agree you can never test too much though. A problem like that delayed my 1.3 release. It turned out I made a small change not too long before submitting to Apple, and tested it fine. Problem was, I didn't test it on a clean install, just kept overwriting my current development app on the iPhone. It turns out I'd introduced a bug that was only seen if you did an install on a device that did not have a previous version already installed!!! Ugh! I won't make that mistake again.
Now, whenever I get ready to submit I follow this:
furbo.org · The final test
What better way to test than to take *the actual distribution build* and strip the Apple signing and swap in your own developer signature. This works great and is close to the experience of downloading it from the App Store as you will ever get until the release/update is live in iTunes!
