Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Best Practices for Testing Mobile  Applications      Presented by Frank Schloendorn1
Let’s continue the conversation!@MaaS360 [Share comments, continue   Q&A, suggest future topics]       #MaaS360Webinar   C...
Poll Question Number One • What is your company’s current position   on testing/certifying mobile applications?   – We do ...
What will I learn? •   Challenges of Testing Mobile Applications •   Knowing the App You Are Testing •   Types of Testing ...
Poll Question Number Two • Which types of mobile apps does your   company test or plan to test?   – In-House developed app...
Challenges of Testing Mobile Applications • Some similarities and differences from testing   traditional desktop/laptop ap...
Know the Application You Are Testing • Is this a in-house developed application? Or one that is from a third   party?     ...
Know the Application You Are Testing • Are there any device ‘Feature’ requirements    – GPS, Wi-Fi, Bluetooth, Acceleromet...
Poll Question Number Three • Do you currently control which   applications a user can install on   their mobile device?   ...
Types of Testing  • Functional     – Same basic rules of traditional application testing     – Does the app perform its fu...
Tools to Aid in Mobile Application Testing  • Emulators    – Available for all major platforms (Android, iOS, WP7      etc...
Tools to Aid in Mobile Application Testing • Virtual Device Testing    – Subscription based    – Multiple Vendors         ...
Tools to Aid in Mobile Application Testing • Automation    – Still in its infancy – not a large selection of options    – ...
Helpful Hints/Things to Remember • When developing in-house enterprise apps, make   sure testing starts when development i...
Helpful Hints/Things to Remember • When possible, have a group of BETA testers to   help with real world testing • Don’t u...
Poll Question Number Four • Which mobile platforms do you plan to   test apps for?   – iOS   – Android   – BlackBerry   – ...
MaaS360 OverviewUser/Device Enrollment   OTA Configuration &         Management  In-depth Inventory &      Device Reportin...
Mobile Device Management Features                                                                           ActiveSync    ...
Network World MDM Product Test  MaaS360 is the Clear Choice Winner  “Fiberlink’s MaaS360 is our Clear Choice Winner, based...
Let’s continue the conversation!@MaaS360 [Share comments, continue   Q&A, suggest future topics]       #MaaS360Webinar   C...
Questions or follow-up?Wrap-up                                                             fschloendorn@fiberlink.com     ...
Upcoming SlideShare
Loading in …5
×

Best Practices for Testing Mobile Applications

8,072 views

Published on

Learn how to test applications for smartphones and tablets in the enterprise.

Learn more: http://www.maas360.com/products/mobile-application-management/

Published in: Technology
  • Be the first to comment

Best Practices for Testing Mobile Applications

  1. 1. Best Practices for Testing Mobile Applications Presented by Frank Schloendorn1
  2. 2. Let’s continue the conversation!@MaaS360 [Share comments, continue Q&A, suggest future topics] #MaaS360Webinar Click the link in the chat window to tweet about today’s webinar @MaaS360
  3. 3. Poll Question Number One • What is your company’s current position on testing/certifying mobile applications? – We do not test/certify mobile applications – We test/certify in-house developed applications – We test/certify in-house and/or third party developed mobile applications 3 3
  4. 4. What will I learn? • Challenges of Testing Mobile Applications • Knowing the App You Are Testing • Types of Testing • Tools/Resources to Aid Testing Efforts • Helpful Hints/Things to Remember 4 4
  5. 5. Poll Question Number Two • Which types of mobile apps does your company test or plan to test? – In-House developed applications – Outsourced developed applications – Third Party applications from the app store/marketplace 5 5
  6. 6. Challenges of Testing Mobile Applications • Some similarities and differences from testing traditional desktop/laptop applications – Multiple platforms (Android, iOS, WP7, etc) – Updates to third party apps are much more frequent and harder to control – Bigger performance concerns (IE – memory, battery) • Fragmentation – Software and Hardware – Primarily an Android concern – Multiple hardware specs (processor, memory, features) • Limited number of tools to help 6 6
  7. 7. Know the Application You Are Testing • Is this a in-house developed application? Or one that is from a third party? – For in-house developed apps, testing should begin with early builds of the application – Development tools should be utilized to profile the application and look for major design flaws (easier to fix sooner than later) – For third party tools, do some research on the company who makes the app • Reviews in the app store/marketplace • Frequency of updates/support options • Company background/reputation • What platforms/OS versions are you supporting/certifying? Does this coincide with the supported stack of the application? – Android (1.x, 2.x, 3.x, 4.x) – iOS (3.x, 4.x, 5.x) – WP7 (7.0, 7.5) – Tablet or Smartphone? – Other? 7 7
  8. 8. Know the Application You Are Testing • Are there any device ‘Feature’ requirements – GPS, Wi-Fi, Bluetooth, Accelerometer, Touch Screen, etc. – Important to know from a device support perspective – Important to know from a performance perspective • Are there any ‘Permission’ requirements – Access Contacts, Access Phone, Access messaging, etc. – Important to know from a security perspective 8 8
  9. 9. Poll Question Number Three • Do you currently control which applications a user can install on their mobile device? – Yes – No 9 9
  10. 10. Types of Testing • Functional – Same basic rules of traditional application testing – Does the app perform its functions as intended? • Usability – Similar to traditional application testing, but with additional caveats – Is it intuitive, does user understand how to use it? – Is it designed for a mobile experience? – Does it fit the familiar look of other mobile applications? – Does it meet the requirements of the platform if controlled by the vendor? (Apple) • Performance – Extremely important for mobile devices – Memory, CPU, and especially power (battery) – Network Utilization also a concern • Upgrade testing – Test both application and OS upgrades 10 10
  11. 11. Tools to Aid in Mobile Application Testing • Emulators – Available for all major platforms (Android, iOS, WP7 etc.) – Good for Basic app testing (functional, user experience) – Not Good for Performance/Resource/Sensor testing – Should never take the place of testing on a real device • Apps for Performance testing – First Party: XCode (iOS) – Third Party: Available through marketplace/app store • Android: System Profiler, Battery Mix, Task Managers 11 11
  12. 12. Tools to Aid in Mobile Application Testing • Virtual Device Testing – Subscription based – Multiple Vendors • DeviceAnywhere • Perfecto Mobile – Remote Access to hundreds of REAL devices • All plaforms – New devices added regularly – Save money over buying your own devices to test with 12 12
  13. 13. Tools to Aid in Mobile Application Testing • Automation – Still in its infancy – not a large selection of options – Built in security of mobile platforms limits capabilities and cross app testing – Virtual device Companies offer automation • Requires dedicated devices on their platform • Costly ($$$) – Third party automation options do exist • Most are platform specific, few are cross platform • Free and paid solutions exist • Most are screen scrapers – Automating mobile application testing generally requires a higher level of programming knowledge • Community Testing 13 13
  14. 14. Helpful Hints/Things to Remember • When developing in-house enterprise apps, make sure testing starts when development is in progress • Know your target platform/devices – Especially true with Android – Know what versions/platforms you will support • Don’t assume that because it works on one device, it will work on all • Don’t underestimate the importance of performance testing • Always have at least a few physical devices available for testing – Especially older ones (iPhone 3GS, early android, etc.) 14 14
  15. 15. Helpful Hints/Things to Remember • When possible, have a group of BETA testers to help with real world testing • Don’t under or over estimate the importance of anecdotal test results • Know the target audience for your application 15 15
  16. 16. Poll Question Number Four • Which mobile platforms do you plan to test apps for? – iOS – Android – BlackBerry – Windows – Other 16 16
  17. 17. MaaS360 OverviewUser/Device Enrollment OTA Configuration & Management In-depth Inventory & Device Reporting Improved Visibility & Control 17
  18. 18. Mobile Device Management Features ActiveSync Apple iOS Android BlackBerry Lotus Traveler> Activate iOS MDM: > Market agent > Supports all EAS or Traveler > Auto-discovery of devices > Apple certificate-based > In-depth OTA connected devices > Auto-discovery of policies > Easy device enrollment configuration and policy > Prevents non-approved > Device activation > Push from admin management devices from accessing > Visibility into device > TouchDown integration: corporate email inventory > User self-service enrollment > Passcode, mandatory > Auto-discovery of devices > Increased actions:> In-depth OTA configuration or disallowed > Auto-quarantine of devices > Send message and policy management: apps, device feature > Alerts and workflows to restrictions, Wi-Fi and > Reset passcode > Passcode, restrictions, approve or block devices email > Change BES policy Wi-Fi, VPN, email, and > Create and enforce profiles, selective wipe ActiveSync policies > Wipe Device more > Increased actions: (e.g., PIN) > Remove device from BES> Increased actions: > Lock, full > Remote device wipe > Refresh data > Full/selective wipe, update, locate, q wipe, lock, update, pass > Support for Exchange 2007 > Support for BlackBerry uery, send & 2010 Enterprise Server 5.0 and code reset message, passcode > Support for Traveler 8.5.2+ higher> Corporate app storefront reset > Exchange or Lotus Notes> Jailbroken device detection > Corporate app storefront > Rooted device detection 18
  19. 19. Network World MDM Product Test MaaS360 is the Clear Choice Winner “Fiberlink’s MaaS360 is our Clear Choice Winner, based on its strong overall performance, particularly its ease of use. The application initially shocked us, as it was comparatively simple to deploy.” 19
  20. 20. Let’s continue the conversation!@MaaS360 [Share comments, continue Q&A, suggest future topics] #MaaS360Webinar Click the link in the chat window to tweet about today’s webinar @MaaS360
  21. 21. Questions or follow-up?Wrap-up fschloendorn@fiberlink.com jpappano@fiberlink.com• Upcoming Webinars (http://maasters.maas360.com/webinars)• Past Webinars (http://links.maas360.com/webinars) – What’s New in 4.0 Android Ice Cream Sandwich? – Building Apps for iPhone and iPad – Securing the Kindle Fire in the Enterprise• Plus lots of How-To content on our website – Mobile Device Management Best Practices • http://links.maas360.com/mdm – Mobile Device Management Glossary • http://links.maas360.com/mdm_glossary• Learn All About the Cloud (AATC) – Presented by The Software & Information Industry Association • http://siia.net/aatc/2012/video.asp 21

×