best practices for testing mobile applications

21
1 Best Practices for Testing Mobile Applications Presented by Frank Schloendorn

Upload: maas360-by-fiberlink

Post on 18-Jan-2015

5.727 views

Category:

Technology


3 download

DESCRIPTION

Learn how to test applications for smartphones and tablets in the enterprise. Learn more: http://www.maas360.com/products/mobile-application-management/

TRANSCRIPT

Page 1: Best Practices for Testing Mobile Applications

1

Best Practices for Testing Mobile Applications

Presented by Frank Schloendorn

Page 2: Best Practices for Testing Mobile Applications

@MaaS360

Click the link in the chat window to tweet about today’s webinar

@MaaS360 [Share comments, continue Q&A, suggest future topics]

#MaaS360Webinar

Let’s continue the conversation!

Page 3: Best Practices for Testing Mobile Applications

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

Page 4: Best Practices for Testing Mobile Applications

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

Page 5: Best Practices for Testing Mobile Applications

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

Page 6: Best Practices for Testing Mobile Applications

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

Page 7: Best Practices for Testing Mobile Applications

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?

Page 8: Best Practices for Testing Mobile Applications

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

Page 9: Best Practices for Testing Mobile Applications

9

Poll Question Number Three

• Do you currently control which applications a user can install on their mobile device?–Yes–No

9

Page 10: Best Practices for Testing Mobile Applications

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

Page 11: Best Practices for Testing Mobile Applications

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

Page 12: Best Practices for Testing Mobile Applications

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

Page 13: Best Practices for Testing Mobile Applications

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

Page 14: Best Practices for Testing Mobile Applications

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.)

Page 15: Best Practices for Testing Mobile Applications

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

Page 16: Best Practices for Testing Mobile Applications

16

Poll Question Number Four

• Which mobile platforms do you plan to test apps for?– iOS– Android– BlackBerry–Windows – Other

16

Page 17: Best Practices for Testing Mobile Applications

17

MaaS360 Overview

User/Device Enrollment

OTA Configuration & Management

In-depth Inventory & Device Reporting

Improved Visibility & Control

Page 18: Best Practices for Testing Mobile Applications

18

Mobile Device Management Features

Apple iOS

> Activate iOS MDM:> Apple certificate-

based> Easy device

enrollment> Push from admin> User self-service

enrollment> In-depth OTA

configuration and policy management:> Passcode,

restrictions, Wi-Fi, VPN, email, and more

> Increased actions:> Full/selective wipe,

lock, update, passcode reset

> Corporate app storefront

> Jailbroken device detection

Android

> Market agent> In-depth OTA

configuration and policy management

> TouchDown integration:> Passcode,

mandatory or disallowed apps, device feature restrictions, Wi-Fi and email profiles, selective wipe

> Increased actions:> Lock, full wipe,

update, locate, query, send message, passcode reset

> Corporate app storefront

> Rooted device detection

ActiveSyncLotus Traveler

> Supports all EAS or Traveler connected devices

> Prevents non-approved devices from accessing corporate email

> Auto-discovery of devices

> Auto-quarantine of devices

> Alerts and workflows to approve or block devices

> Create and enforce ActiveSync policies (e.g., PIN)

> Remote device wipe> Support for Exchange

2007 & 2010> Support for Traveler

8.5.2+

BlackBerry

> Auto-discovery of devices

> Auto-discovery of policies

> Device activation> Visibility into device

inventory> Increased actions:

> Send message> Reset passcode> Change BES policy> Wipe Device> Remove device from

BES> Refresh data

> Support for BlackBerry Enterprise Server 5.0 and higher

> Exchange or Lotus Notes

Page 19: Best Practices for Testing Mobile Applications

19

Network World MDM Product Test

“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.”

MaaS360 is the Clear Choice Winner

Page 20: Best Practices for Testing Mobile Applications

@MaaS360

Click the link in the chat window to tweet about today’s webinar

@MaaS360 [Share comments, continue Q&A, suggest future topics]

#MaaS360Webinar

Let’s continue the conversation!

Page 21: Best Practices for Testing Mobile Applications

21

Wrap-up• 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

Questions or [email protected]

[email protected]