7 steps to pragmatic mobile testing Vancouver

© 2014 SOASTA. All rights reserved. June 25, 2015 1



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



!  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


Technology

7 steps to pragmatic mobile testing Vancouver