In this 5-part blog series, we will take a deeper-dive into each step for launching a continuous delivery strategy. In part 2, we will focus on the importance of testing and debugging on real mobile devices.
How does testing and debugging on real mobile devices benefit continuous delivery and agility?
Now that you understand the importance of setting up a device cloud for mobile development, testing and QA, it’s time to move on to the next step in launching a continuous delivery strategy.
As an enterprise mobility team, all team members face diverse challenges regardless of their role. Naturally, due to the fast-paced, mobile first environment that we are operating in, a large portion of the tasks for an enterprise mobility team revolves around the customer experience. Customers, whether external or internal users, are the ones who live in the apps you create daily. They are the ones whose objectives, expectations and mobile experiences color the types of apps and mobile experiences that your team has been tasked to create. In other words, mobile users have high expectations and your team better deliver.
No matter how you are testing today, with real devices or using simulators and/or emulators, it is important to remember that your users are interacting with the real thing. Therefore, your team should test on real mobile devices to accurately mimic the environment that your users are seeing when they interact with your app. As a nod to agility, if a problem should occur debugging on real devices can save the team time by catching the problem at its source and fixing it where it lives.
Real Devices = Real Results
Perhaps Motown legends Marvin Gaye and Tammi Terrell said it best in 1968 when they sang that there, “Ain't nothing like the real thing, baby.” Although the duo was singing about love, and mobile devices did not exist, we can apply this sentiment to testing on real mobile devices.
Since your users are engaging with real devices, it only makes sense to also develop and test on real devices. Real devices produce real results. Real results enable your team to debug and fix any issues that arise on the real platform quickly and efficiently.
Although it is tempting to use the free simulators and emulators that come with iOS and Android development environments, remember that you get what you pay for.
Simulators and emulators run on a desktop being processed by a desktop processor and memory, while the devices run ARM compatible chips, which is a completely different architecture from a real device. Running on a real device allows you to see exactly the type of computing power is required to run your app.
Do you have a process that consumes the CPU? You may get an approximate guess on a simulator, but how does it run on the latest device, or even the entry level device? If it uses a lot of the CPU, chances are your app will also consume a lot of battery. The same goes for memory. Various real devices have different memory configurations. Much like the simulator, the memory is an approximate guess. It isn’t the same memory that is on a real device. A real device can give you the answers you need.
deviceConnect has features that allow you to view the
memory, CPU, and power of real devices allowing you to know for sure that you
have a performing application.
Don’t believe us? Apple has the following in their testing guides:
Tip: To avoid issues later when you distribute your app, you should test your app running on actual devices.
Want to learn more about continuous delivery and setting up a device cloud? Download our recent webcast to learn more about the 5 steps to launch a continuous delivery strategy and the benefits of testing and debugging on real devices.