Developing A Mobile Testing Strategy

In today’s mobile-first world, a good app is important, meaning an effective Mobile Testing strategy is  essential.  

We recently started working with a new client on a Mobile Testing project. As with many mobile-first and mobile-only companies, their first question was how to develop a Mobile Testing strategy for ensuring quality in this constantly shifting mobile landscape. For starters, building out a Mobile Testing strategy requires several dimensions including:

  • Functional
  • Platform Compatibility (OS/Devices)
  • Network Variances
  • Performance
  • Test Automation
  • Integration
  • Usability and User Experience

Each of these mobile QA and test strategy dimensions are summarized below.

Mobile Functional Testing

When you approach Mobile Functional Testing, you need to start with the type(s) of mobile application (Pre-Installed Mobile Applications, Native Mobile Applications, Mobile Hybrid, Mobile WebApp, Mobile Website, etc.) you’ll be working on and then build out the important characteristics to be tested for each type. Functionality is assumed across platforms, but there are many other platform specific functionality differences and considerations.

Mobile Platform Compatibility

Because a mobile application must be compatible with native device features and not interfere with or inhibit common functions, mobile QA needs to incorporate the capabilities and limitations of different device/OS platforms in order to differentiate defects from platform limitations. With so many permutations and combinations to test, it’s critical to have a strategy for prioritizing the combinations to be tested. With such a large number of test permutations, simulators and remote devices provide reasonable alternatives. In the end, you’ll need a combination of real, emulated, and remote devices and have to figure out when it’s best to use each option.

Network Variances

One of the special aspects of Mobile App Testing is that it involves more than the mobile phone or application. Network configurations can significantly impact your application’s performance and impact your test environment. Network variations including 2G, 3G, 4G, LTE, CDMA, GPRS, GSM, HSCSD, SIM, and WAP should make up a critical part of your test matrix depending on your target market. Adding 5G will only increase complexities.

Mobile Performance

Performance is much more complicated with mobile applications as the pieces are disjointed and not well integrated. There are 3 main components: server, network, and mobile device with application. You need to be cognizant of each component while determining your strategy based on the type of mobile application discussed above. Many don’t prioritize Performance Testing as they should, only to realize way too late.

Mobile Test Automation

As with regular Automation, Test Automation for mobile follows the same rules; it makes no sense to automate where it’s not economical. Don’t automate tests that aren’t run often or tests that will need to be changed frequently due to an application that is changing often. There are many Automation tools available, some open source and commercial. In the end, Mobile Automation concerns are much deeper than tools.

Integration

With the popularity of wearables and IoT devices, the importance of integration comes to the forefront. Almost all wearables are dependent on the mobile smartphone as a communications and processing hub. Inherent in their functionality is communication with the smartphone either through WIFI, Bluetooth or NFC, and sometimes a combination. The usage of these interfaces and the gathering of data broadens the concerns for security and privacy.

Usability and User Experience

Getting a product out that is functional is not enough. Touch enabled and haptic interfaces make the interaction between the user and the device more direct and personal. The distance between user and device is reduced not just physically but also emotionally, and users create a relationship with the device, hence the importance of user experience in mobile applications.

Summary

If you’re developing a mobile app, you probably didn’t realize all the things that go into assuring its quality. In the end, it takes more than the ‘wow’ factor in screen design.

Philip Lew
Philip Lew is the CEO at XBOSoft. As a Corporate Executive, Development Manager, Product Manager, and Software Engineer, Philip has managed teams to tackle broken processes, develop solutions to difficult problems, and coached others to be leaders, managers, and experts. He leverages his academic background in Operations Research and Computer Science combined with hands-on work experience in programming, predictive modeling, and algorithm development to work with clients and colleagues around the world in improving their software processes.

The Related Post

It’s a bird! It’s a plane! It’s a software defect of epic proportions.
VISTACON 2010 – Keynote: The future of testing THE FUTURE OF TESTING BJ Rollison – Test Architect at Microsoft VISTACON 2010 – Keynote   BJ Rollison, Software Test Architect for Microsoft. Mr. Rollison started working for Microsoft in 1994, becoming one of the leading experts of test architecture and execution at Microsoft. He also teaches ...
Steps that will enable you to identify the weaknesses of your new app, its vulnerabilities and strengths. So you’ve just finished developing a nifty, customisable app that can help farmers track their produce from source to market via their mobile phone. You’re elated and want to get started marketing it right away. Not to burst ...
Introduction This article discusses the all-too-common occurrence of the time needed to perform Software Testing being short changed as specification, development, and unforeseen “issues” cause the phases prior to testing to expand. The result is that extreme pressure is placed upon the testing organization to perform the testing function within a reduced time frame. The ...
At VISTACON 2011, Jane sat down with LogiGear Sr. VP, Michael Hackett, to discuss complex systems.
I’ve been intending to write a book review of How We Test Software At Microsoft, by Alan Page, Ken Johnston, and Bj Rollison, but for whatever reason I just never found the time, until now. In general, I like this book a lot. It’s a nice blend of the tactical and the strategic, of the ...
Testing appears to be the least popular topic in Android development circles based on the relatively few books on Android app testing. Most tend to focus on development because, unfortunately (but true), application testing isn’t be something most developers think much about, or if they do, they don’t do it systematically (I’m guilty of this ...
At VISTACON 2011, Harry sat down with LogiGear Sr. VP, Michael Hackett, to discuss various training methodologies. Harry Robinson Harry Robinson is a Principal Software Design Engineer in Test (SDET) for Microsoft’s Bing team, with over twenty years of software development and testing experience at AT&T Bell Labs, HP, Microsoft, and Google, as well as ...
Do testers have to write code? For years, whenever someone asked me if I thought testers had to know how to write code, I’ve responded: “Of course not.” The way I see it, test automation is inherently a programming activity. Anyone tasked with automating tests should know how to program. But not all testers are ...
The Testing Domain Workbook is the most extensive and exhaustive work you will ever find on a specific testing technique (or related techniques if you include equivalence class analysis and boundary testing as the book does). What I like best is the combination of academic background and roots combined with practical experience and industrial practice. All the concepts are ...
LogiGear Magazine March Issue 2018: Under Construction: Test Methods & Strategy
D. Richard Kuhn – Computer Scientist, National Institute of Standards & Technology LogiGear: How did you get into software testing? What did you find interesting about it? Mr. Kuhn: About 10 years ago Dolores Wallace and I were investigating the causes of software failures in medical devices, using 15 years of data from the FDA. ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe