Seven Steps to Pragmatic Mobile Testing

Mobile testing is getting harder—more devices, multiple operating systems, higher quality expectations, and shorter development cycles. How do you deal with these demands? In order to align mobile testing with product strategies and market goals, Tom Chavez says you first need to (1) know your users and how they will use your app. (2) Knowing the app and how users may actually be using it differently are key to testing to satisfy users—not the designers. (3) With test case matrices vastly larger than ever, prioritizing tests into “must-haves” and “nice-to-haves” is necessary to make the testing process manageable. With so many devices on the market, you have to (4) determine which are required for testing, which are optional, which to purchase, and which you might borrow or rent from a device cloud. Tom advises (5) how to know which tests to automate, which should remain manual, and (6) how back-end performance affects user experience. And finally, (7) know your edges. Learn the key strategies for mobile testing and this seven-step process with the tools you can use to deliver the testing to meet your project goals.