"The Final build"
"During the early days of iPhone software development, there were no mechanisms for doing beta tests. Those of us on the bleeding edge were developing apps with very little peer review and beta testing.
But this essay isn�t about reminiscing. It�s about telling you how to test the applications you upload to iTunes Connect.
If you�ve submitted an application to the App Store, you know that sinking feeling of not being able to test your final build. The binary that gets signed with the �App Store� distribution mechanism cannot be run on your test devices: you can�t be sure that the final bits you send to Apple are complete.
But there�s a simple way around this problem and it�s called codesign. The same application we used for our pre-Ad Hoc beta testing can also be used for a final test on your App Store submissions.
The first step is to create your distribution build for the App Store. For this example, we�ll be using the Frenzic application and putting it into build/Distribution-iphoneos. After the build completes, make the ZIP file archive immediately. Put it in a safe place so you can upload it to iTunes Connect after you finish your final test.
Now you can move the updated application onto a test device and make sure that the final build is OK. Everything except the signature is the same: if there�s a missing file or something that�s messed up, you�ll be able to find it before the QA engineers at Apple do (and with 10 day turnaround times, that�s a very good thing.)
Once you�re happy that everything looks good, upload the ZIP file you created earlier to iTunes Connect and crack open a beer. As you�re enjoying that beer, take a look at the codesign man page for more information on this essential utility. Or write an essay for your web log :-)
Updated July 2nd, 2009: Note that this procedure can also be used if you are beta testing. This is particularly helpful in cases where you�ve upgraded to an iPhone 3GS and the Ad Hoc .mobileprovision file for the beta contains the UDID for your older device. Many developers have hit the 100 device limit since the release of the new phone, and can�t add devices into a new .mobileprovision file. You�ll be able to test the beta releases after signing the code with your own certificate. The only case where this won�t work is when the app being resigned uses the keychain."
Download full version rtf
Also:
A Overview of Game Testing Techniques.pdf
LINK
Testing the final product BEFORE distribution is essential. When a car rolls of the Ford production line it gets tested...You cannot final test a product until its finished.