An Introduction toMobile-UI Automated   Testing Tools            Craig Wilson   Software Quality Engineer, EMC2           ...
UI Automation• Automated testing from end-user’s  perspective• Validate appearance and functionality• Rudimentary performa...
Automation Paradigms
Automation Paradigms     Visual           Programmatic No interaction with Use application code to  application code   int...
Automation Paradigms     Visual           Programmatic No interaction with Use application code to  application code   int...
Automation Paradigms     Visual           Programmatic No interaction with Use application code to  application code   int...
Automation Paradigms     Visual           Programmatic No interaction with Use application code to  application code   int...
The big questionHow do I test on a physical         device?
Not “can”, “how”
Not “can”, “how”• Jailbreaking required• Application code must be modified• Functionality may be reduced• As always, read t...
Device integration• Multitouch gestures?• Hardware controls? - Screen lock, volume, etc.• Alert invocation? - New message,...
Other considerations• Platform support• Additional coding requirements• Learning curve• Compatibility with continuous inte...
Personal observations• No clear “best-in-class” tool for all  platforms• Platform and device restrictions still  prevalent...
Questions?
Upcoming SlideShare
Loading in …5
×

Introduction to Mobile-UI Automated Testing Tools

2,104 views

Published on

A 5-minute overview of mobile-UI automated testing tools given at DevTO on September 26, 2011.

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • Is it possible to automate UI elements such as button area, font type, font size, button alignment using automation tools without the use of source code or apk files?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total views
2,104
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
36
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • - Use folder name truncation bug (in EMC Mobile) as example of difference between the verification methods\n- Programmatic verification can also be selective: verify text, state, location, etc.\n- Last points refer to what will change more: the appearance of your UI, or how you code it?\n\n
  • - Use folder name truncation bug (in EMC Mobile) as example of difference between the verification methods\n- Programmatic verification can also be selective: verify text, state, location, etc.\n- Last points refer to what will change more: the appearance of your UI, or how you code it?\n\n
  • - Use folder name truncation bug (in EMC Mobile) as example of difference between the verification methods\n- Programmatic verification can also be selective: verify text, state, location, etc.\n- Last points refer to what will change more: the appearance of your UI, or how you code it?\n\n
  • - Use folder name truncation bug (in EMC Mobile) as example of difference between the verification methods\n- Programmatic verification can also be selective: verify text, state, location, etc.\n- Last points refer to what will change more: the appearance of your UI, or how you code it?\n\n
  • \n
  • - TestPlant’s “eggPlant” is an example for the first point.\n- FrogLogic’s “Squish” is example of second point, leads to build complexity.\n- Also bring up cloud solutions like DeviceAnywhere where you remotely access devices from a shared pool.\n
  • - Instruments can do a lot of these\n- Gestures are very important for mobile!\n
  • - Easy example for second point: Instruments, with its requirement for accessibility labels.\n- Learning curve isn’t just the scripting language, but also how the application is written.\n- examples of additional capabilities: screenshots, multiple scripting language support, movie recording, etc.\n
  • \n
  • \n
  • Introduction to Mobile-UI Automated Testing Tools

    1. 1. An Introduction toMobile-UI Automated Testing Tools Craig Wilson Software Quality Engineer, EMC2 @DarkOxygen
    2. 2. UI Automation• Automated testing from end-user’s perspective• Validate appearance and functionality• Rudimentary performance analysis
    3. 3. Automation Paradigms
    4. 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. 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. 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. 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. 8. The big questionHow do I test on a physical device?
    9. 9. Not “can”, “how”
    10. 10. Not “can”, “how”• Jailbreaking required• Application code must be modified• Functionality may be reduced• As always, read the fine print
    11. 11. Device integration• Multitouch gestures?• Hardware controls? - Screen lock, volume, etc.• Alert invocation? - New message, low battery, etc.
    12. 12. Other considerations• Platform support• Additional coding requirements• Learning curve• Compatibility with continuous integration processes• Additional capabilities
    13. 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. 14. Questions?

    ×