This document discusses performance testing for mobile applications. It outlines the importance of performance testing given the growth of mobile platforms and users' tendency to abandon apps with performance issues. It then describes various types of mobile apps and some common performance challenges. The rest of the document provides techniques for testing aspects like network performance, battery usage, and memory consumption on different mobile devices and networks. It also lists some tools that can be used for performance testing of mobile apps.

1. PERFORMANCE TESTING
FOR MOBILE APPLICATION
By
Hunza Basharat
Sr. SQA Engineer in folio3

2. AGENDA
Type of Mobile Application
Why Performance Testing is Important
Performance Challenges

3. CONTINUE
Techniques
Tools
Q/A

4. TYPE OF MOBILE APPLICATION
Mobile Browser apps
 mDOT-.‐dedicated mobile sites
 Responsive web design
Native Apps
 Hybrid Apps

5. IMPORTANCE OF PERFORMANCE
TESTING
 With the fantastic growth of mobile computing
platforms there has been a dramatic increase in the
value of mobile applications for most companies.
 While developing a mobile application its important to
make it free from performance issues
Having variety of applications available, user abandon
the use of application that lacks in performance

6. PERFORMANCE CHALLENGES
 Mobile Browsers Apps
 Network Performance
 Server Response Time
Native Apps
 Memory leaks
 CPU limit
 Network/Bandwidth
 Power consumptions

7. CONTINUE
 Hybrid Apps
 Response Time
 Caching Issue

8. TECHNIQUES
Testing in various network strengths
 No Network
 Low
 Medium
 High
Testing during change of network strength from:
 No Network/Low to High
 High to Low/No Network

9. CONTINUE
Testing in various network types:
 2G
 GPRS
 EDGE
 3G
 4G
 Wi-Fi

10. CONTINUE
 Monitoring Battery consumption patterns
 Observe battery consumption rate as the application
is being
 Run in Background
 Run in Foreground
 Run the application for long time.

11. CONTINUE
Check memory usage patterns (ROM consumption)
when in device
 No other applications are installed
 Lot of free memory available in device.
 Some third party applications are installed
 Lesser free memory available in device
 Lot of third party applications are installed
 Very less free memory available in device

12. CONTINUE
Memory Consumption Pattern (RAM usage)
 Check memory consumption pattern when multiple
applications are running while the application is being:
 Launched
 Run
 In Background
 In Foreground
 In Background/idle for long period of time

13. FEW POINTERS FOR IOS APP
SUBMISSION
App size should not be more than 50 MB for non--
‐gaming app.
Any memory leak and your app is rejected
Device battery constraints
Excessive heating

14. TOOLS
 NeoLoad (commercial tool for native/browser based/hybrid
apps)
 Apache JMeter (open source for browser based/hybrid apps)
 HP LoadRunner (commercial)
 Charles Proxy (open source for monitoring the web services)
 AppthWack (commercial tool for device fragmentation)
 AT&T Application Resource Optimizer (ARO) (free, and cross-platform
tool for optimizing mobile app performance)

15. Q/A