19
Mobile application testing: How to perform transition from web testing to mobile testing

Mobile application testing

Embed Size (px)

DESCRIPTION

Learn how a web tester can move to mobile application testing. Softheme's presentation for SQA Days 2012

Citation preview

Page 1: Mobile application testing

Mobile application testing:

How to perform transition from web testing to mobile testing

Page 2: Mobile application testing

Mobile applications popularity

• standalone applications for all platforms – about 1 mln.

• mobile websites – even more

Mobile application testing has become a typical task in most of IT outsourcing companies

Page 3: Mobile application testing

Common features of web and mobile testing

• Browser compatibility checks• Evaluation for different screen

resolutions• Similar instruments

(emulators of browsers/ devices)

It is not hard for a web tester to switch to mobile devices

Page 4: Mobile application testing

Setting testing objectives

• What are we testing – mobile website or mobile application

• For whom – user profile (geogrphy, technical skills, expectations etc.)

• Devices – which models and/or emulators will be used for testing

• How – defining approaches (Friends & Family testing, scenario-based etc.)

Page 5: Mobile application testing

Testing mobile website

• Define suppported browsers

• Define test coverage• Move on to testing

Web testers are familiar with the process

Page 6: Mobile application testing

Mobile application testing• select platforms (iOS,

Android, Blackberry, Windows Mobile, Symbian, Bada)

• screen resolutions, supported by the application (for instance, it is critical for Galaxy Tab)

• hardware requirements (GPS, multitouch etc.)

Page 7: Mobile application testing

Platforms and versions coverage

• Popularity of Symbian and iOS is steady

• Android is on the rise

• Blackberry loses market share

(worldwide stats)

Page 8: Mobile application testing

Mobile platforms stats

Статистика по США, источник - http://gs.statcounter.com

Page 9: Mobile application testing

Screen resolutions

• iOS = iPhone + iPad + iPod

• Andoid = screen + OS

• Blackberry = almost like Android

Page 10: Mobile application testing

Screen resolution of iOS devices

Source: http://developer.apple.com

iPhone Original/3G/3GS: 320 × 4804/4S: 640 × 960

iPad 1024×768

iPod 1—3 generation: 320 × 480 px, 163 ppi4-е generation: 960 × 640 px, 326 ppi

Page 11: Mobile application testing

Screen resolution of Android devicesLow density (120), ldpi

Medium density (160), mdpi

High density (240), hdpi

Extra high density (320), xhdpi

Small screen 240x320 480x640

Normal screen 240x400240x432

320x480 480x800480x854600x1024

640x960

Large screen 480x800480x854

480x800480x854600x1024

Extra large screen

1024x600 1280x8001024x7681280x768

1536x11521920x11521920x1200

2048x15362560x15362560x1600

Source: http://developer.android.com

Page 12: Mobile application testing

Testing for Blackberry

• Versions and devices:

us.blackberry.com http://supportforums.blackberry.com

• Devices and resolutions Wikihttp://stats.wikimedia.org

BlackBerry and more

Page 13: Mobile application testing

Coverage is defined. Now what?• Buy many mobile devices?• Download many

emulators and simulatiors of mobile devices and browsers?

• Submit to multiple online services to gain access to all mobile devices?

Page 14: Mobile application testing

Option 1: Purchasing devices

Pros:• Real user

environment• Tech specs are clear• High speed of testing

Cons:• Expensive• Not always possible

to buy/order devices• One device = One

QA Engineer• Get out of date

quickly

Page 15: Mobile application testing

Option 2: Emulators and simulatorsPros:• They are free• Speed of testing is

higher than on physical devices

• Can be easily provided to all QA Engineers

Cons:• They can’t emulate all

types of user interaction• Don’t provide clear tech

specs• Exist not for all devices

Page 16: Mobile application testing

Option 3: services that provide remote access to devices

Pros:• Cover virtually all devices• Provide instant access• Cost less than purchasing all

the devices

Cons:• Don’t provide 100%

interaction• Relatively slow• Still costly – sometimes it’s

cheaper to buy devices

Page 17: Mobile application testing

Friends & Family testing

• One person – one device• Variety of real-life interactions• Fast and easy• Real user experience• New unexpected bugs• Quick informal feedback

Everyone has a mobile device nowadays, that is

why for smoke testing it makes sense to gather a group friends, family and acquaintances

Page 18: Mobile application testing

Let’s summarize

Mobile application testing is:

• Easy to perform – it can be described with a check-list, there is no complex fucntionality

• Easy to plan – coverage is defined by exploring current usage stats

• Inexpensive – we can use emulators, online services and use Friends&Family approach

• Challenging – variety of models and OS versions

Page 19: Mobile application testing

Thanks!

About Softheme: Softheme provides QA and testing services for desktop, web and mobile applications since 2009.More than 30 mobile applications successfully released.