Mobile users have high expectations for apps, with nearly 80% deleting apps after first use due to bad design, slow loading, or crashes. Testing mobile apps is challenging due to a variety of devices, platforms, and user expectations. An effective mobile testing strategy uses a combination of emulators, physical devices, cloud/mobile testing tools, and both automated and manual testing methods across the application lifecycle to ensure quality, performance, and reliability.

1. Mobile Testing Strategy
by QAProgrammer.com

2. Mobile User Expectations
Mobile users have far higher expectations of mobile apps when compared
to other software like browser applications. The majority of reports and
surveys state that nearly 80% of users delete an app after using it for the
first time! The top four reasons for deletion are always bad
design and usability, loading time and crashes immediately after
installation.
▪Nearly 60% of users will delete an app that requires registration.
▪47% of consumers expect to load in 3 seconds or less.
▪50% of user will delete an app due to crashes.

3. Mobile Testing Challenges

4. Mobile Testing Solutions
4 Device Repository - Devices, Assets
4 Test Coverage
4 Mobile App Testing CoE in an Agile Environment.
4 To execute a successful QA manual, automation or combination strategy on
time and on budget.
4 MTCoE is platform independent, making true end-to-end testing with a single test script possible.
4 Continually monitor usage and feed data into the analysis to refine test configuration selection.
4 Understand the application technology, business objectives and user profile
4 Subject Matter Experts leveraging various available tools and solutions
4 Translation of interface and language specific to local requirements.
4 Specialize in providing quick and the best possible return on investment
through our low cost of localization testing services.
4 Increasing test automation to reduce manual effort

5. Mobile Application Test Strategy
Emulators Physical Devices
Cloud /Mobile
Testing Tools
40 - 50% 20%30 - 40%

6. Types of Mobile Testing

7. Mobile App Lifecycle
➢ Mobile applications once developed and
tested ready for deployment are directly
submitted to “Application Stores” of the OS
providers for their approval.
➢ Once approved the Mobile applications are
available for download from the respective
OS providers “Application Store”.
➢ End customers can directly download your
application from these “Application stores” on
their mobile devices to use the same.

8. Mobile Lab :Tools and Platforms
Automation Tools Platforms Manufacturers
MonkeyTalk iOS Apple
Appium Android OS RIM
Selenium Blackberry OS Nokia
Robotium Windows Mobile Motorola
experitest Symbian HTC
QTP Sony Erricson
Jmeter Samsung
NeoLoad LG
VeraCode Micromax

9. Mobile Tools and Software

10. Mobile Application Testing

11. CI Through Mobile Testing
Frame Work
» Integrated with Continuous Integration environment
» Leverage automation testing frame work
» Simple to use interaction layer that let's running automated test
» Run configurable automated tests
» Initiate automated tests remotely
» Feedback loop for improving user
» experience and make better architectural and development decisions

12. CI Through Mobile Testing
Frame Work

13. CI Through Mobile Testing
Frame Work

14. Types of Testing

15. Agility Testing
Agility: Best practices on Agile including automation focus and effective intraday
QA practices form the core of the solution
Types of testing : Testing includes Acceptance testing at build level, Functional ,
Interruption (NFR) and Regression at Sprint level and also Release Regression
Continuous automation and Regression: Automation will be leveraged to
execute acceptance tests at build level and regression tests at sprint level and
across sprints
Devices/ Platforms coverage: Optimal set of devices have been considered
/assumed to ensure adequate coverage in the target platforms
Quality management: Best in class methods for leveraging Test management
processes and Tools best suited to agile needs.

16. Cloud Based Test Automation
Developers
Source
code
Code
Repository
Build
failed
Successful
build
QA & Testers Error reporting
Test Cases
Application
Users / Consumers
Commit

17. Secure Mobile Lab Facility
• PCs , MAC machines & different mobile platforms connected to appropriate server for applications
• Necessary Wi-Fi router, SIM cards, with internet connection
• Necessary firewall and Ethernet switch for networking to specific WAN/Networks
• The networking could be an isolated network
nvironment
• Controlled wireless with limited range with security protected environment
• Have firewalls and switches within lab premises
• All internet access to be monitored with limited connectivity
• Antivirus and security software on devices for enhanced security
work Security
• Authorized entry with usage of swipe/similar means for usage of the LAB depending on need.
• Entry and exit recording in physical /electronic means to keep track
• Restrict usage of personal mobile phones, USB drives or other media
sical Security
www.qaprogrammer.com