Testing. No one really wants to do it. It’s expensive. It’s time consuming. But unfortunately, it’s needed to ensure that your consumers have a positive experience when they use your mobile applications. And it’s vital that you make sure that the experience is a great one for every consumer every time they use your application, starting with that very first time. Fail to do a good job of testing and your customer will end up doing it for you—and unlike your testing team, your customers don’t have the tools or the time to report back problems. And keep in mind that your customers don’t want to be treated like guinea pigs. When they find a fault, they simply never come back, and you’ll never hear a word from them.
The goal of your testing efforts is not to find errors. Perhaps your developer has actually done a great job and did not make any mistakes. Instead, your goal in testing should be to understand the quality of your offering. Does it work? Does it function as expected? Will it meet the needs of your users, so that they come back again and again?
But when it comes to testing mobile applications there are unique challenges. The challenges of mobile testing present you with tradeoffs that you need to consider and choices that you need to make about the mix of different techniques and methods that you will use in testing. Each testing choice you consider will have pros and cons associated with it, and you will probably find that no one testing choice will be completely satisfying. Rather, you will need to consider a testing strategy that combines different testing options that together provide you with the best overall testing result that balances the tradeoff between cost, quality, and time-to-market.
In this document, we examine the various testing options for mobile applications while explaining the factors that you will need to consider in determining your testing strategy. Finally, we make some recommendations on how you can combine the various testing options to find the testing strategy that fits your mobile application.
Mobile Testing Challenges for Native Applications
To many, “mobile apps” have become synonymous with native applications (and hybrid applications). Commonly downloaded from an App store, they offer the user a unique experience that maximizes the capabilities of the device & operating systems for which they are developed. The app download is often controlled by the gate-keeping app store, with mechanisms in place to charge potential consumers. This simple and proven monetization model has fueled native apps very popular in the development community. Beyond their acceptance in the consumer market, they also allow enterprises to deliver productivity tools to an increasingly mobile workforce.
While native applications can provide a rich experience to the user—and possibly a lucrative one for the developer—they also add some complexity to the lives of those tasked with testing them.
Testing needs to ascertain that the app can be successfully downloaded to the device, executed on the device and interact with the supporting back content infrastructure. When updates are made you need to be sure that the application can to be pushed out to and accepted by the end user. There’s a misperception that successful testing of app functionality on one device provides assurance across all others of the same operating system.
Native applications are tied to the hip with the hardware and operating systems for which they are written. To meet the challenge of testing for native mobile applications, it’s essential to test on the physical devices supported by your application. You’ll also want to ensure backward compatibility with each older generation of the device you’re expected to support. Owning and maintaining a version of each device can be expensive and burdensome. Consistency in executing your test plan is also a problem when you’re limited to manual testing from a proverbial closet of mobile devices. Finally, you’ll want to be sure that when issues are found with your native apps that they can be quickly captured and shared with others.
Mobile Testing Challenges for Web Applications
Like the Web itself, a mobile Web application is viewable by users around the world. Even if you’re initially targeting only users in a single country or on a single network, it helps to understand the global dynamic.
When we test mobile Web applications we encounter several challenges presented by the nature of the global, mobile Web. As we understand the nature of each challenge, we can explore different technology options to manage issues and mitigate risk. Coming up with the right solutions for your requires an assessment of the advantages and disadvantages inherent in each of the testing options available to you and determining the technology that best suits your testing requirements. These mobile testing challenges include devices, network, and scripting.
Devices: The Biggest Mobile Testing Challenge
The mobile devices used by consumers create the most obvious challenge to mobile Web testing. There are potentially tens of thousands of different client devices that could be used to access your mobile app or website, and they must therefore all be considered when testing your mobile applications. This number can be reduced to an extent, but each time you reduce the number of device types that you test against, you are taking a chance that your application might not work on a device, locking out a number of potential customers.
To handle the device challenge, you have three options: You can test exclusively using real devices, you can test exclusively with emulated devices, or you can use a combination of each.
Real devices have the advantage of having all of the limitations and quirks present in the actual client hardware and firmware combination in the hands of your target consumers. However testing with real devices can be expensive, depending on how you go about it. They are expensive to buy—and forget about the advertised prices, for those are the operator-subsidized prices that come only with a contract that has its own cost implications. You might be able to get a manufacturer or network operator to loan you devices for testing, but you need to join a waiting list and convince the hundreds of manufacturers and hundreds of mobile network operators that you should be a priority. Airtime and subscription costs also need to be paid. And finally, testing with real devices can be disorganized and labor intensive if the testing environment is not conducive to creating, collecting and reproducing results in a consistent manner.
Emulated devices, on the other hand, are relatively easier to manage. You can switch device types by simply loading a new device profile, and instantly you have a new device that presents itself to your mobile Web application in the same way that the real device would. And because the emulators run on more powerful PCs and servers and were designed with testing in mind, they are typically fully instrumented to capture detailed diagnostics about the protocols that go back and forth between client and server at the various levels of the stack.
When you encounter an application fault, you will have the information to isolate and thus correct the problem. Emulated devices are thus cost effective, because a single platform with frequent updates of device profiles can be used to test every device on the market both today and tomorrow.
The big disadvantage of emulated devices is that they lack the quirks, faults and characteristics that only the real device can provide. An emulated device may not give the pixel-perfect accurate rendering that you’re assured to have with a real device solution. And while the processing power of your local PC can be an attribute, it will also hide any issues that you may have with the responsiveness of your Web application. Finally, an emulated device is not sensitive to the ambient conditions that can impact the behavior of the device. In the majority of cases this is a good thing, however if you want to know how well a device performs in an exact location such as a crowded stadium, a real device is your better bet.
Fortunately you’re not limited to an either/or selection when determining the right device solution for your mobile testing needs. A third approach is to select a mix of both emulation and real device testing. First start testing in an emulated environment to take advantage of the speed and device diversity that an emulator can provide. Emulated device testing early in the development cycle can help you achieve these goals at a relatively low cost. Early in the development cycle you don’t need the pixel-perfect rendering afforded by an actual device. The risk of not having the nth degree of certitude is easily outweighed by the benefits gained by increasing the number of test cases and device types covered in the test suite. Add real devices into your test plan later in the development cycle so you can add validate the applications are functioning as expected and certify that all development requirements and objectives have been met.
Network: A Regional Challenge
There are well over 400 mobile network operators in the world.
Each mobile operator may support multiple network technologies including LTE, CDMA, GSM, and some use less common or local networking standards such as iDEN, FOMA, and TD-SCDMA. Each network has a unique combination of network infrastructure that tunnels the packet-based protocols used by mobile networks into TCP-IP protocols used by the mobile Web. Each network operator has implemented systems that behave slightly differently from different vendors to perform the required tunneling. Lastly, most network operators have inserted mobile Web proxies (that is, the gateway) to dictate how, when, and if you are able to connect to a particular site. When a network operator implements a mobile Web proxy, it can restrict the flow of information that travels between your server and the test client. Some proxies limit the sites that can be accessed via a phone to only those approved by the operator in what is often referred to as a “walled garden.” Other proxies might use “transcoding” in an attempt to scale down fixed Web content to better fit onto mobile phones, thus expanding the number of mobile sites that can be seen—and unfortunately they might also “transcode” your made-for-mobile application. Finally, some proxies strip vital information from the HTTP headers that your application might depend on to provide functionality or to provide device adaptation. As you can see, the network challenge has a lot of complications to it.
It’s not possible to discuss the network challenge without discussing location. It’s a simple fact that to fully test the full network stack on a particular operator’s network infrastructure, you must be connected to the target network. But the challenge is made more difficult by the fact that the radio signals are not strong on cellular networks, so you must be adjacent to a cell connected to the operator’s core network to run your test. Thus, if you want to test against SFR, you must be in France, and if you want to test against China Mobile, you must be in China.
Obviously, traveling to every network operator that you need to support can be very expensive, and there are obvious cost tradeoffs to be considered.
There are different ways of dealing with network challenge it. We can bypass the lower layers of the network and simply test over the Internet or LAN, or we can use the real network by using either phones or modems.
When you bypass the network’s lower layers, you use TCP/IP to connect directly to the server and you ignore the GPRS tunneling systems used by network operators. Since most real devices are not capable of doing this, you will need to use a device emulator to perform the bypass. Not all device emulators support this feature, and you may want to look for a device emulator that can perform network bypass by using the Internet. Some device emulators also have the ability to access the operator’s proxy (but only if it is exposed to the Internet) to allow a more realistic test. Even if the operator’s Web proxy is available to only its customers, there are test proxies on the Internet that can be used. Even if you don’t have a test proxy, you will still be able to test directly against your origin Web server.
An advantage of bypassing the network is that you will not need to use and thus pay for airtime. And because you are using a device emulator, you again benefit from having a fully instrumented stack.
The disadvantages of network bypass are that is that we often cannot emulate the effects and timing of the network and the various network elements such as proxies. Finally, when you use this technique, you can’t use real devices and thus don’t see the quirks and limitations that real consumers will see.
Naturally, it is possible to test against real networks. One method is to use real devices at the target location, though you will face many of the problems already discussed. Alternatively, many device emulators support modems that allow you to use your emulated devices on the local network—but again there is the cost of traveling into range of the network. But there is another option.
One piece of useful test equipment is a real device in the cloud. This type of testing solution consists of a physical handset mounted in a remote box with a remote control unit and a remote antenna. The remote control unit is physically connected to the device’s screen and keypad control circuits and is capable of pressing keys and collecting screen images. Exposed to the Internet, this solution lets a user on a local PC or Web client control a device with their mouse and keyboard, and thereby see what is happening remotely on the screen. These devices provide an elegant solution that can be connected to either live networks or simulated networks, although most rely on live networks.
Remote real device solutions often have the ability to record a test for subsequent replay, a capability that can be useful for regression testing.
Real device in the cloud reduce the cost of travel to foreign networks, but still can be expensive because the cost of the device is now amplified by the cost of the remote control hardware, remote control software, and local software. Because there are so many different makes and models of devices, it is often too expensive to buy a remote real device solution for all the devices that you need to test against. Fortunately, most of the companies that make this type of equipment offer the ability to “rent” testing time on a resource that is shared with others and is managed for you. You simply need to open an account, and you then buy testing time with a given make and model of device when and where you need it.
Scripting: The Repeatability Challenge
Our last challenge of mobile testing is what we call scripting, the method that is used to actually execute the test script. Script execution can either be manual or automated. You either write down the scripts in a document or a spreadsheet, which is then used by a test engineer who manually enters keystrokes, or you run automated scripts that in turn evoke the keystrokes and record the results.
Because there are so many different devices with different menu structures and keystroke options, automated scripting needs to be abstracted away from the device to be of any real use. Consider a script that follows strict keystrokes on an Apple iPhone. This script would not have any chance of working on a Nokia N70, because the user interfaces are completely different. Fortunately, most automated testing software provides high-level scripting functions such as “goto URL” or “send SMS”, which are not dependent on the particular menu structure of the target device. Most device emulators are capable of automating test execution using a higher-level, abstracted scripting language that is not device dependent.
When you use automated scripting, the cost of setting up the script will typically be higher than the cost of a single manual execution of a test script. But if it is a test script that you run on a periodic basis, every time that you subsequently run the script, the more time and effort you will save. If you run the script enough, you will eventually recover the cost of initial scripting.
Finally, many automated scripting tools have a special ability to “spider” or “crawl” a mobile Web site. This is a special capability that can test an entire site with a single command. Although this capability will not be able to perform complex transactions, it is a quick test to set up that will walk your mobile Web site looking at every page for errors and device inconsistencies and is a very powerful and cost-effective tool.
Hopefully, you now understand a lot more about the challenges associated with mobile testing of native and web applications. But what do you do with this information? What should be your testing strategy for mobile application testing?
First, it is not a matter of choosing one tool or technique; there are simply too many compromises that must be made. Most likely you will need to use a combination of testing tools and techniques to meet your quality requirements. But generally you can narrow your choices down based on the following recommendations:
Keynote is the leading provider of on-demand test and measurement solutions for continuously improving the mobile experience.
Keynote’s DeviceAnywhere platform is the industry’s leading real device, remote testing solution providing developers, testers and QA teams large and small alike access to hundreds of real smartphones, feature phones and tablets. The DeviceAnywhere platform patented Direct-to-Device® technology enables state of the art mobile testing from anywhere in the world. Users get full mobile device interaction, including complete hardware controls and pixel-perfect image and text display.
Keynote also provides a leading emulated mobile Web testing solutions with its Mobile Internet Testing Environment (MITE). MITE can emulate over 2,200 device profiles with more than 12,000 user agent strings and also allow remote testing in 7 global locations.