iPhone/iPad testing tips and testing utility
Provide
'crash reporter' logs with your defect reports. Each time an iPhone application
crashes, a .crash file is created on your iPhone. You can retrieve this file
when you synch your iPhone with iTunes. Here's a link that describes where
those files are stored: iPhone Crash Logs locations are:
Mac OS X
~/Library/Logs/Crash Reporter/Mobile Device//
Windows XP
C:\Documents and Settings\\Application Data\Apple computer\Logs\Crash Reporter\\
Windows Vista
C:\Users\\AppData\Roaming\Apple computer\Logs\Crash Reporter\Mobile Device\\
Create connectivity problems. If you're testing an iPhone app that depends on internet connectivity, then test for degraded or unavailable connectivity. It's easy to make connectivity unavailable by simply turning on Airplane Mode. To degrade connectivity, especially on Edge or 3G, employ some sort of metallic "shield" on top of your iPhone.
Gather up UDIDs (unique device identifiers) early. This is a simple logistics task but seems to be one that becomes critical as the first build approaches. And it's a hassle for the Dev team to add new UDIDs and create new provisioning files as each new person wants to install an application during development. Get the UDIDs of all know devices that will be used during testing and set a cut-off date for the addition of any new devices. Check out Find UDID with a single click. You can also connect all your iPhones and iPods touches to your computer and use the iPhone Configuration Tool to collect UDIDs.
Employ background applications. But the iPhone can only have one application running at a time, right? That's true for those of us that develop and test applications, but not for Apple. Applications that continue running in the background on the iPhone are Safari, iPod and Mail. And what about reminders and push notifications? These "interrupters" can affect the behavior of an application under test.
Also, since iPhones and iPod touches are devices that users buy primarily to use as a phone or a music player, it’s important to test that an app can gracefully handle situations where the user receives a call or plays music from their music library (iTunes) while the app is running. We’ve seen issues here where apps aren’t smoothly multi-functioning in these areas.
Spy on the app from the console. iPhone apps will report application and system level warnings to the console. You can view these warnings in real-time using Apple's iPhone Configuration Tool. By knowing what's being reported when interacting with an app can help you refine the steps you need to reproduce tricky (and memory related) problems.
Configuration profiles are XML files that contain device security policies, VPN configuration information, Wi-Fi settings, APN settings, Exchange account settings, mail settings, and certificates that permit iPhone and iPod touch to work with your enterprise systems.
Test under low memory conditions. This relates to #1 above. You'll be able to tease additional crashing bugs if you force free memory to a very low level, e.g. < 2MB, before proceeding with your tests. One way to do this is to open several Safari windows before you start your testing.
Speed Test – This is another simple yet useful iPhone utility that measures the network speed of your iPhone.
(
) to check the battery status
WiFi locator: WiFiFoFum scans for 802.11 networks and gives you a plethora of information about each it detects:
System Activity Monitor allows you to check your:
• Run time (RAM) memory usage
• Storage (Disk) usage
• All running processes
• CPU usage
• Wi-Fi and Cellular IP addresses
• MAC addresses
• Device information
• Battery level
The free Disc Space allow to check available space..
It’s one thing if someone e-mails you a link to look at, another thing entirely if they e-mail you a Word file or a PDF.A relatively new app, File Viewer
URL status: You can monitor FTP, HTTP and HTTPS network protocols.
thanks,
Yours Kalyan.
Mac OS X
~/Library/Logs/Crash Reporter/Mobile Device//
Windows XP
C:\Documents and Settings\\Application Data\Apple computer\Logs\Crash Reporter\\
Windows Vista
C:\Users\\AppData\Roaming\Apple computer\Logs\Crash Reporter\Mobile Device\\
Create connectivity problems. If you're testing an iPhone app that depends on internet connectivity, then test for degraded or unavailable connectivity. It's easy to make connectivity unavailable by simply turning on Airplane Mode. To degrade connectivity, especially on Edge or 3G, employ some sort of metallic "shield" on top of your iPhone.
Gather up UDIDs (unique device identifiers) early. This is a simple logistics task but seems to be one that becomes critical as the first build approaches. And it's a hassle for the Dev team to add new UDIDs and create new provisioning files as each new person wants to install an application during development. Get the UDIDs of all know devices that will be used during testing and set a cut-off date for the addition of any new devices. Check out Find UDID with a single click. You can also connect all your iPhones and iPods touches to your computer and use the iPhone Configuration Tool to collect UDIDs.
Employ background applications. But the iPhone can only have one application running at a time, right? That's true for those of us that develop and test applications, but not for Apple. Applications that continue running in the background on the iPhone are Safari, iPod and Mail. And what about reminders and push notifications? These "interrupters" can affect the behavior of an application under test.
Also, since iPhones and iPod touches are devices that users buy primarily to use as a phone or a music player, it’s important to test that an app can gracefully handle situations where the user receives a call or plays music from their music library (iTunes) while the app is running. We’ve seen issues here where apps aren’t smoothly multi-functioning in these areas.
Spy on the app from the console. iPhone apps will report application and system level warnings to the console. You can view these warnings in real-time using Apple's iPhone Configuration Tool. By knowing what's being reported when interacting with an app can help you refine the steps you need to reproduce tricky (and memory related) problems.
Configuration profiles are XML files that contain device security policies, VPN configuration information, Wi-Fi settings, APN settings, Exchange account settings, mail settings, and certificates that permit iPhone and iPod touch to work with your enterprise systems.
Test under low memory conditions. This relates to #1 above. You'll be able to tease additional crashing bugs if you force free memory to a very low level, e.g. < 2MB, before proceeding with your tests. One way to do this is to open several Safari windows before you start your testing.
Speed Test – This is another simple yet useful iPhone utility that measures the network speed of your iPhone.
(
) to check the battery status
WiFi locator: WiFiFoFum scans for 802.11 networks and gives you a plethora of information about each it detects:
System Activity Monitor allows you to check your:
• Run time (RAM) memory usage
• Storage (Disk) usage
• All running processes
• CPU usage
• Wi-Fi and Cellular IP addresses
• MAC addresses
• Device information
• Battery level
The free Disc Space allow to check available space..
It’s one thing if someone e-mails you a link to look at, another thing entirely if they e-mail you a Word file or a PDF.A relatively new app, File Viewer
URL status: You can monitor FTP, HTTP and HTTPS network protocols.
thanks,
Yours Kalyan.
Comments
Post a Comment