seven steps to pragmatic mobile testing

T4 Mobile Testing 10/6/16 9:45

Seven Steps to Pragmatic Mobile Testing Presented by:

Tom Chavez

SOASTA

Brought to you by:

350 Corporate Way, Suite 400, Orange Park, FL 32073 888-‐-‐-‐268-‐-‐-‐8770 ·∙·∙ 904-‐-‐-‐278-‐-‐-‐0524 -‐ [email protected] -‐ http://www.starwest.techwell.com/

Tom Chavez Tom Chavez has more than twenty years of experience as a manager and product manager in the software development tools field. Today, he works in product management as a senior evangelist at SOASTA. Tom has worked across the Silicon Valley at companies including Apple, Sun, PalmSource, and Intuit delivering tools for Mac, Java, PalmOS, Linux, and Android development and testing. He speaks frequently at industry conferences and meet-‐ups on topics including web app performance and testing at large scale, mobile continuous integration and testing, automated mobile testing tools, and big data analytics for business value. Follow Tom on Twitter @TomChavez.


o Expanding Test Plans



o Shorter Product Cycles




o More Device Platforms





o A Changing Focus





o A Changing Focus

o An Emphasis on Analysis


Time

Duration

Location

Intent

TIP: Work with your product owner, review market

research, conduct user focus groups, and verify/validate

with real user monitoring


Developers intended execution paths

User common use paths


Developers intended execution paths

User common use paths

User revenue generating patterns

Current problem areas

TIP: Use real user data to create test cases


Core functions and experiences

Core differentiators

Edge functions

Complicated

Repetitive

Measure manual effort

Know your person days per cycle, per area

TIP: Use your matrix to know which tests to automate


Rank active devices

Analyze device usage

Weight matrix to device

Know problem areas per device

Core devices to own

Edge devices to borrow/rent

TIP: Choose which devices you must own

for testing and which might be optional but available

based on real user monitoring


Start ASAP

Simple

Time Consuming

Mundane

Rhythm

TIP: Goal is Continuous Integration execution


Device reaction to app functionality

Battery, CPU, Memory…

Common user path

Speed per screen or page

Separate back and front end performance

Performance to revenue correlation/transaction or task completion

TIP: Prioritize tests to highest revenue producing/completion paths


Mobile Performance is more than just App Performance


Time to Market

Functional

Competitive

TIP: Prioritize which strategy you will apply with the time saved from

test automation


Know your:

1. User

2. App

3. Matrix

4. Devices

5. Plan to automate

6. Performance

7. Edge

seven steps to pragmatic mobile testing

Software