User:Shoaib.shafique

iPhone Applications testing Tips

1. Accurately report available memory. Memory problems are one of the non-reproducible bugs that occur before related free memory. 2. Provide 'crash reporter' logs with your defect reports. Each time an iPhone application crashes, a iTunes. 3. Spy on the app from the console. iPhone apps will report application and system level warnings to the console. what's tricky 4. Test under low memory conditions. This relates to #1 above. You'll be able to tease additional crashing tests.

5. Screenshots, screenshots, screenshots. Nothing makes a UI bug stand out for a developer than when you click 6. Provide useful defect characterization information. Developers always like to have help in their debugging a there's under 3.x. 7. Create connectivity problems. If you're testing an iPhone app that depends on internet connectivity, then turning metallic 8. Boundary test data input. Wherever an iPhone app asks for text input, you have an opportunity to find field. You'd be surprised at how this trips up some apps. Additionally, we’ve been finding that application errors are generating when entering the following characters into text fields: !@#$%^&*_. (Note: Holding down letters (A, E, I, O, etc) or symbols ($, !, &, etc) on the onscreen keyboard generates a keyboard popup that includes localized and 2-byte characters. 9. Gather up UDIDs (unique device identifiers) early. This is a simple logistics task but seems to be one UDIDs development. for your iPhones and iPods touches to your computer and use the iPhone Configuration Tool to collect UDIDs. 10. Employ background applications. But the iPhone can only have one application running at a time, right? continue and Also, that library functioning in these areas.

reference:

frndszone.com