Mobile App performance testing mainly tests whether the App runs under extreme conditions such as boundary and pressure to meet customer needs, for example, whether the App runs normally when the battery is insufficient and the number of visits increases.
(1) Non-functional testing An important aspect of app testing is the non-functional requirements of the app. Before the mobile app is launched on the market or undergoes further development, testers have certain responsibilities to track such requirements. To measure app performance to be done in the early development phase should be a usability test. Usually done by alpha users or colleagues. Walk into a café or restaurant and ask the people inside about their app usage. Give them a look at the first version at this stage of development and gather feedback to see if users are using the new features well to get a first impression. (2) Functional testing Every new function developed needs to be tested. Measure app performance is an important aspect of app testing. Testers should perform manual testing and post-automation testing maintenance. At the beginning of testing, testers have to manually test the app as a "black box" to see if the provided functions are correct and function as designed. In addition to classic software testing, like clicking a button, submitting an order and seeing what happens, testers must perform more functional app testing. Apart from the whole manual testing process, test automation is also important for mobile apps. Every code change or new feature may affect existing features and their state. Usually there is not enough time for manual regression testing, so testers have to find a tool to perform automated regression testing. Now there are many automated testing tools on the market, both commercial and open source, for different platforms, such as Android, iPhone, WindowsPhone7, BlackBerry and mobile Webapp. Depending on the development strategy and structure, quality management testing specialists need to find out which automation tools are best suited for their environment. (3) Client-side measure app performance Whether an App is doing well or not is not only reflected in its functions. The performance of the tested app on low-end and mid-range devices is also important. For example: a very fun game or application can only run smoothly on high-end machines, but it will not work well on low-end and mid-end machines, and it will not gain a good reputation. Regarding the measure app performance of the App, the parameters we are more concerned about are: CPU, memory, power consumption, traffic, FPS. At the same time, it is also necessary to pay attention to the installation time and startup time of the App. At present, a question that may be confusing to everyone is, how high is the CPU, memory, power consumption, traffic, and FPS to meet the published values? Here I can tell you that you can refer to some values of high-quality games, and compare the app data developed by yourself with the high-quality app data in the industry.
Mobile App performance testing mainly tests whether the App runs under extreme conditions such as boundary and pressure to meet customer needs, for example, whether the App runs normally when the battery is insufficient and the number of visits increases. The following introduces the main points of performance testing of mobile apps.
1. Boundary testing
Under various boundary pressures, such as insufficient power, insufficient storage space, and unstable network, test whether the App can respond correctly and run normally.
2. Stress test
Constantly exert pressure on mobile apps, such as increasing load and increasing data throughput, to determine the service bottleneck of the app, obtain the maximum service level that the app can provide, and determine whether the performance of the app meets user needs.
3. Responsiveness test
Responsiveness testing is essentially a stress test, whether the App can respond correctly under certain conditions, and whether the response time exceeds customer needs.
4. Energy consumption test
Test the resource occupation of mobile devices when the App is running, including memory and CPU consumption, power consumption and traffic consumption when the App is running for a long time, and verify whether the resource consumption of the App meets user needs.
