This content is part of the Essential Guide: Enterprise architects' guide to success with mobile apps for business
Get started Bring yourself up to speed with our introductory content.

FAQ: Testing mobile app performance

Mobile app performance testing comes with unique challenges. Associate site editor Caroline de Lacvivier answers some FAQs to help you get started.

Testers accustomed to Web and desktop environments are faced with entirely new challenges in mobile quality assurance. The testing community, limited by devices and network conditions, has had to reassess its priorities. The current focus is on simplifying apps without sacrificing user experience. Developers and testers alike must find creative ways to emulate realistic user scenarios in order to build, monitor and update applications that customers will find a joy to use.

For those just entering mobile testing’s complex arena, here are some answers to frequently asked questions that will help to get started.

How is mobile app testing different from Web app testing?

Software teams transitioning to mobile should expect challenges that require an entirely new approach to quality assurance. For one thing, the lifecycle is shorter and software updates are more frequent, which creates the need for more testers.

Software teams transitioning to mobile should expect challenges that require an entirely new approach.

Time-to-market has become so competitive that mobile releases are rushed out the door before all the kinks are worked out. For this reason, more updates are required to smooth out the wrinkles and to keep data relevant to different devices as well as changing operating systems.

Testers are much more central in this scenario than they were in the past. Traditionally, there was one tester for every three (or more) developers. Now, mobile requires one tester for every developer.

What are the first steps to take in mobile testing?

Mobile testers need to learn to anticipate the real-world challenges users face. This means accounting for variable network conditions, limited battery power and device constraints. Testing expert Matt Heusser suggests purchasing real devices rather than relying on emulators and simulators to mimic user scenarios. For all their sophistication, they can never be as accurate as the real thing.

Should testing practices be different depending on the app?

A tester's priorities will shift depending on the purpose of the app as well as its intended user. According to Scott Sehlhorst, the primary focus for B2C applications should be to encourage widespread adoption. This means focusing on simplicity, functionality and design (i.e., user experience).

Alternatively, B2B and B2E applications can mandate usage and therefore do not need to focus as much on fostering customer participation. It is crucial, however, for enterprise applications to have a dependable security policy, one that protects both company and private user information. Since BYOD has blurred the line between business and personal devices, it also falls to development teams to build applications with cross-platform technologies. This means considering the constraints of different devices and testing for each.

What mobile security concerns should I be aware of?

In terms of software, mobile security concerns are much the same as those in desktop and Web apps. The main difference is that portable devices can be lost or stolen. This means that developers will need to consider the way in which data is stored so that, if the device does fall into the wrong hands, sensitive information is protected.

One method is encryption. Developers might also store data in random-access memory so that it’s accessible to the application but hidden from view. Code signing is another protective measure in which a digital signature is attached to application binaries so that a source can be authenticated.

Security expert Dan Cornell also recommends creating a diagram of all the systems and databases the mobile app interacts with. This visual portrayal can be useful because it shows developers and testers how data moves through the app and at which points security might be threatened.

How do I account for variable network conditions?

Software teams have to consider network variability early in the development process, according to SearchSoftwareQuality expert Jen Lent. Mobile apps that are proactively designed for speed and simplicity will be less vulnerable to network interference. Furthermore, define how the app should behave when a phone switches from WiFi to 3G, then test it. Walk the device into a dead zone to see how it maintains functionality with a lost or weak connection.

What skills are most valuable in the mobile space?

The best mobile apps not only have an intuitive user experience but also have a high-quality user interface (UI). Such design skills are not necessarily primary in desktop and Web development and are therefore relatively hard to come by. Many development teams grapple with a UI design skills gap, according to tech journalist Crystall Bedell, particularly because devices and operating systems change so quickly that even talented designers have trouble keeping pace.

How do I approach tight release cycles?

Though it may seem counterintuitive, the popular approach is to limit initial testing, release applications in their infancy and then update often, depending on the problems that crop up. When it comes to mobile apps, updates are so frequent that users have come to tolerate and expect them. In fact, many updates run in the background without any user initiation. This makes post-release improvements much easier. SearchSofwareQuality expert Kevin Parker says it’s also useful to automate the parts of the lifecycle that can be automated, freeing up workers to pay attention to the parts of the lifecycle that matter.

Dig Deeper on Topics Archive

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

What is your biggest mobile testing challenge?
simulation and emulation
I thought mobiles are so user-centric that it throws up a whole host of possibilities when it comes to how different users will interact with the same 'app' under test.
@rsri80ram , that's a good point. Mobile users in the wild can show a lot of variation. Would you rather focus efforts on figuring out which users to include in your testing scenarios or developing testing scenarios so broad you catch most users? That's not rhetorical. I honestly think either of those could be a practical approach. Personally, I'd rather focus in on a smaller audience to reduce variation, but I can imagine situations where generalizing might be necessary.
My biggest challenge is in Load and Performance Testing.
Testing of applications during offline/aeroplane mode, as well, landscaping with native, hybrid & web applications are challenges with different version in Android, iPhone, windows mob..,
Security testing for accessibility, authentication, etc..,
Endurance, Peak, Avg load testing, pinching & expanding, how the mobile behave if it is half broken..,
Even a couple of years later, I second kirankumarreddy: simulation and emulation. Still the biggest challenge. There are SO many devices out there!
Cross-device testing. But I'd ask why it's a challenge that testers has to deal with? These costs must be considered in architectural decisions.
This is a great read! When it comes to mobile apps, there’s nothing more important than ensuring they perform like they’re supposed to. Once a user has a bad experience with an app, they rarely give it another go.

I have one quick addition to these FAQs based on what I typically hear from customers: how do I better manage the entire mobile testing process?

As mobile testing becomes more sophisticated, it is critical that developers adhere to the agreed-upon software development lifecycle and QA guidelines. This process can go much more smoothly if you integrate with a test management solution that helps deliver control and collaboration within testing environment. Planning, executing, and even automating your mobile test scripts will go much more smoothly and you’ll have an end product that you can rely on.

— Michael Wright, Micro Focus