WTA-74: Organizing Your Environment for a Mobile App Testing Session

WTA-74: Organizing Your Environment for a Mobile App Testing Session

WTA-74: Organizing Your Environment for a Mobile App Testing Session

Date: 8-13- 2016 (1:00 p.m. – 3:00 p.m.)

Facilitator: Jean Ann Harrison

When conducting tests for a Mobile App, the number of test management can get overwhelming. Because you’re testing an entire system beyond the GUI, Test ideas start to blend and important tests can be lost. This Weekend Testing Americas session, we will focus on using an organizational method of managing your testing of a mobile app.

We offer the following sample categories and feel free to suggest your own ideas during the session.

A. Functional testing

– Works as designed?

– Consistent with the purpose?

B. UX testing

– Perceivable? (Font size, contrast, screen size and rotation)

–  Readable? (Text and images understandable and useful, hints, help links, etc.)


C. App performance

– App response and performance

– Multiple apps

– The app in background

– The app in sleep mode

D. Device performance with the app

– Battery levels

– Battery drain/charge

– CPU load and stress

– Hot/cold temperature

E. Storage and Memory

–  Required to install

–  Memory usage

–  Starving conditions

–  Cloud memory

F. Network

– Connectivity

–  Speed

–  WiFi access

–  Cellular access

G. Workflow

–  Start/end points

–  Steps

–  Loops

–  Interruptions (push notifications, timeout, etc)

–  Termination/restart

Testing Sessions

  1. Observation and learning
    • Learning about the interface and functionality
  2. Usage scenarios
    • Following common and uncommon usage scenarios
  3. Function and data 
    • Exploring aspects of behavior of a function (valid/invalid steps, conditions, data boundaries, etc.)
    • Trying applicable data combinations
  4. Bug hunt
    • Deliberately trying erroneous / invalid operations and conditions

Product under test:

MapQuest (Maps, Navigation, and Directions)

Recommended: have the app installed prior to the session.

Mission: Based on the sample categories coverage and testing sessions, come up with a testing strategy for the selected product. Consider that each session is one hour long. Consider that you have a budget of 8 hours.

About the Author

I’m a software tester working with Socialtext in Palo Alto, CA. I have worked in a number of different fields and in a number of different capacities. I started my testing career in March of 1991. I am co-founder and primary facilitator for Weekend Testing Americas. I am a black-belt in the Miagi-do School of Software Testing, a member and Teacher in the Association for Software Testing, and the producer of Software Test Professionals' "This Week in Software Testing" podcast (now on hiatus).