Devices The Biggest Mobile Testing Challenge -meyou

Web-Development Here we are with another topic in our Testing Strategies and Tactics for Mobile Apps series. In the first Part we discussed on two important things i.e., Mobile testing challenges for native apps and web apps. Prior to that today we are going to talk about the biggest challenges involved in mobile devices testing. 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 .bination of each. Real devices have the advantage of having all of the limitations and quirks present in the actual client hardware and firmware .bination 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 buyand forget about the advertised prices, for those are the operator-subsidized prices that .e only with a contract that has its own cost implications. You might be able to get a manufacturer or .work 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 .work operators that you should be a priority. Airtime and subscription costs also need to be paid. And finally, testing with real devices can be dis.anized 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 youre 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 youre 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 dont 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. About the Author: 相关的主题文章: