This document provides an overview of automated testing tools for mobile user interfaces. It discusses two main paradigms for automation: visual testing, which verifies the appearance of UI elements without interacting with application code, and programmatic testing, which uses application code to interact with and verify UI elements. The document cautions that both approaches need to account for intended visual changes and code changes that don't affect layout or appearance. It also addresses questions around testing on physical devices and considerations like device integration, platform support, and compatibility with continuous integration processes.

1. An Introduction to
Mobile-UI Automated
Testing Tools
Craig Wilson
Software Quality Engineer, EMC2
@DarkOxygen

2. UI Automation
• Automated testing from end-user’s
perspective
• Validate appearance and functionality
• Rudimentary performance analysis

3. Automation Paradigms

4. Automation Paradigms
Visual Programmatic
No interaction with Use application code to
application code interact with UI elements
Verify
Verify presence and state
appearance of UI
of UI elements
elements
Beware of code changes
Beware of intended
that don’t affect layout or
visual changes
appearance.

5. Automation Paradigms
Visual Programmatic
No interaction with Use application code to
application code interact with UI elements
Verify
Verify presence and state
appearance of UI
of UI elements
elements
Beware of code changes
Beware of intended
that don’t affect layout or
visual changes
appearance.

6. Automation Paradigms
Visual Programmatic
No interaction with Use application code to
application code interact with UI elements
Verify
Verify presence and state
appearance of UI
of UI elements
elements
Beware of code changes
Beware of intended
that don’t affect layout or
visual changes
appearance.

7. Automation Paradigms
Visual Programmatic
No interaction with Use application code to
application code interact with UI elements
Verify
Verify presence and state
appearance of UI
of UI elements
elements
Beware of code changes
Beware of intended
that don’t affect layout or
visual changes
appearance.

8. The big question
How do I test on a physical
device?

9. Not “can”, “how”

10. Not “can”, “how”
• Jailbreaking required
• Application code must be modified
• Functionality may be reduced
• As always, read the fine print

11. Device integration
• Multitouch gestures?
• Hardware controls?
- Screen lock, volume, etc.
• Alert invocation?
- New message, low battery, etc.

12. Other considerations
• Platform support
• Additional coding requirements
• Learning curve
• Compatibility with continuous integration
processes
• Additional capabilities

13. Personal observations
• No clear “best-in-class” tool for all
platforms
• Platform and device restrictions still
prevalent
• iOS: Try Instruments first, then consider
other tools

14. Questions?