A recent client needed some testing help with their iPad web app–but not on the iPad. The web app’s rollout was so successful that an executive decree was made to support it on “all mobile devices” (!), and that meant testing a pretty long list of web-enabled mobile devices that the web app was never designed for.
Or did it?
Take a look at this three-part article over at SearchSoftwareQuality where DeveloperTown’s Rick Grey describes a strategy for mobile application testing on a budget, using a contextual and incremental approach to avoid breaking the bank (while still addressing critical risks/coverage needs).
Part 1, Mobile application testing: Mobile devices on a budget, sets the stage for the complexity of testing and support for “all” mobile devices.
Part 2, Mobile application testing: Cost effective strategies, looks at a five-point strategy to responsibly shrink the problem space.
Part 3, Mobile Web applications: Monitoring test triggers, looks at an approach to monitoring test triggers for the web app and its supporting systems to manage testing requests and expectations.
The series isn’t designed to be a prescriptive answer to all mobile testing situations. Instead, it encourages considering context to make sure you’re getting value out of testing and that your stakeholders know what they’re getting for their investment in testing. Be sure to check it out!
