7 steps to pragmatic mobile testing Vancouver
0 likes•374 views
The document outlines strategies for expanding test plans and highlights the need for adapting to shorter product cycles, a variety of device platforms, and a shifting focus towards analysis. It emphasizes the importance of using real user data to inform test case creation and prioritizing tests based on revenue-generating user paths. Additionally, it advocates for a structured approach to device usage and test automation to enhance efficiency in the testing process.
7 steps to pragmatic mobile testing Vancouver
- 1. © 2014 SOASTA. All rights reserved. June 25, 2015 1
- 2. © 2014 SOASTA. All rights reserved. June 25, 2015 2
- 3. © 2014 SOASTA. All rights reserved. June 25, 2015 4 o Expanding Test Plans
- 4. © 2014 SOASTA. All rights reserved. June 25, 2015 5 o Expanding Test Plans o Shorter Product Cycles
- 5. © 2014 SOASTA. All rights reserved. June 25, 2015 6 o Expanding Test Plans o Shorter Product Cycles o More Device Platforms
- 6. © 2014 SOASTA. All rights reserved. June 25, 2015 7 o Expanding Test Plans o Shorter Product Cycles o More Device Platforms o A Changing Focus
- 7. © 2014 SOASTA. All rights reserved. June 25, 2015 8 o Expanding Test Plans o Shorter Product Cycles o More Device Platforms o A Changing Focus o An Emphasis on Analysis
- 8. © 2014 SOASTA. All rights reserved. June 25, 2015 9 ! Time ! Duration ! Location ! Intent TIP: Work with your product owner, review market" research, conduct user focus groups, and verify/validate" with real user monitoring
- 9. © 2014 SOASTA. All rights reserved. June 25, 2015 10 ! Developers intended execution paths ! User common use paths
- 10. © 2014 SOASTA. All rights reserved. June 25, 2015 11 ! Developers intended execution paths ! User common use paths ! User revenue generating patterns ! Current problem areas TIP: Use real user data to create test cases
- 11. © 2014 SOASTA. All rights reserved. June 25, 2015 12
- 12. © 2014 SOASTA. All rights reserved. June 25, 2015 13 ! 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
- 13. © 2014 SOASTA. All rights reserved. June 25, 2015 14 ! 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
- 14. © 2014 SOASTA. All rights reserved. June 25, 2015 15
- 15. © 2014 SOASTA. All rights reserved. June 25, 2015 16
- 16. © 2014 SOASTA. All rights reserved. June 25, 2015 18 ! Start ASAP ! Simple ! Time Consuming ! Mundane ! Rhythm TIP: Goal is Continuous Integration execution
- 17. © 2014 SOASTA. All rights reserved. June 25, 2015 21 ! 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
- 18. © 2014 SOASTA. All rights reserved. June 25, 2015 22
- 19. © 2014 SOASTA. All rights reserved. June 25, 2015 23 ! Time to Market ! Functional ! Competitive TIP: Prioritize which strategy you will apply with the time saved from" test automation
- 20. © 2014 SOASTA. All rights reserved. June 25, 2015 25 Know your: 1. User 2. App 3. Matrix 4. Devices 5. Plan to automate 6. Performance 7. Edge
- 21. © 2014 SOASTA. All rights reserved. June 25, 2015 26