This document discusses seven steps for accelerating mobile testing. Mobile testing is fundamentally different than traditional testing due to differences in development processes, team structures, release frequencies, testing matrices, user expectations, and quality measures for mobile apps. The seven steps recommended are: 1) think like a mobile user, 2) decide between real devices or emulators, 3) implement smoke tests for basic functionality, 4) get developers involved in testing, 5) start with simple automation techniques, 6) implement continuous integration, and 7) use both manual and automated testing methods. The goal is to remove barriers and speed up the mobile testing process.

1. Chris Karnacki
Senior Solutions Consultant
Keynote
Seven Steps to Remove Barriers and
Accelerate Mobile Testing
May 26, 2015

2. Mobile testing is fundamentally different!
© 2015 Keynote, LLC
DESIGN-DRIVEN
DEVELOPMENT
CONTINUOUS
DELIVERY
EXPERIENCE-
DRIVEN
ANALYTICS
IDEA
THE PROCESS IS DIFFERENT
THE LIFECYCLE REDEFINED
Designers : 1
Developers : 2-4
Quality : 1-2
Mobile architects : 1
THE TEAM SIZE IS DIFFERENT

3. Mobile testing is fundamentally different!
© 2015 Keynote, LLC
The release frequency is different
Release velocity has moved beyond
enterprise control.
OS’s (e.g., iOS, Android, Windows)
#Formfactors/devices
The NxN testing matrix is different
This isn’t your grandmas’ Windows + IE
matrix anymore.

4. Mobile testing is fundamentally different!
© 2015 Keynote, LLC
User expectations are different
User expectations are at an all time
high. Tolerance for a poor UX is at an
all time low.
Quality is different
Who owns quality? Dev or QA? Mobile
teams have a different structure.
for any digital interaction to load1
3SECONDS OF
TOLERANCE
The user is king

5. Skills, collaboration, consistency
© 2015 Keynote, LLC
“Why can’t you reproduce this error, Number One?”

6. Just get me on the road
to recovery, please.
© 2015 Keynote, LLC

7. The seven step program to removing barriers and
speeding up mobile testing
© 2015 Keynote, LLC

8. Think like a mobile app user
© 2015 Keynote, LLC
1. What do I need to do without any reading
anything…is it clear what I need to do?
2. What’s the key user journey’s?
3. What doesn’t work? What are the simple ways to
work around the key user journey
• Fuzz testing
• Negative testing
• Exploratory testing

9. Real device testing or emulators?
© 2015 Keynote, LLC
iOS emulators
Android emulators
device lab by Jeremy Keith on Flickr

10. Smoke tests…who needs them? EVERYONE
© 2015 Keynote, LLC
1. app launch
2. login
3. key first common action
4. logout

11. Get your developers involved!
© 2015 Keynote, LLC

12. Automate, automate, automate ... but start simple!
© 2015 Keynote, LLC

13. Who needs continuous integration? EVERYONE
© 2015 Keynote, LLC

14. Manual and Automation
Functional Testing
 Improves coverage / quality with
functional testing for mobile apps
and websites
 Robust and resilient automation
(object level support) to shorten
release cycles
 Largest cloud library of real iOS and
Android devices; zero device
management
 Remote access for geographically
distributed teams
 Day 1 support for new OS releases
Functional testing powered by the cloud
© 2015 Keynote, LLC

15. Questions?

16. Thank you
© 2015 Keynote, LLC