Mobile app performance Test index _app test

Performance testing plays an important role in the application of quality assurance, which is summarized in three aspects: application of client performance testing, performance testing applied on the network, and testing of server-side performance. Under normal circumstances, three effective and reasonable combination, can achieve comprehensive analysis of system performance and bottleneck prediction.

Through the performance test tool to obtain the test object's each performance index, compares each performance index with the industry standard value or the competition product value to make the comprehensive conclusion and the optimized improvement plan. The following is an example of a typical app, such as a hand tour, that describes the client performance metrics in detail.

　　

Inclusion

Package size can be listed as performance indicators, from the app performance indicators and game operations two dimensions, the player is more likely to be small packages at the same time performance is better, sometimes they will be a trade-off between the relationship.

　　

CPU occupancy Rate

In general, the use of mainstream mobile phone game 20%-40% CPU occupancy rate is reasonable, of course, this number with the recent increase in mobile phone hardware configuration, will be slightly reduced, if the CPU occupancy rate of more than 80% it is worth our attention.

Number of frames (FPS)

A rendering that can be used to indicate whether a page is smooth. Mobile game frame rate fps,30-60 are acceptable, on the 60 for the subjective feelings of the human eye is not very different. For game development, not the higher the FPS must be better, FPS depends on the video card, followed by memory, CPU, and then the network. Therefore, the overall game of other performance indicators, choose a suitable fps can be.

Memory usage

In Android, each app process uses private memory alone, in addition to sharing (shared dirty) with other processes, and usually uses PSS (= private memory + proportional allocation shared memory) to measure the memory overhead of an app. The memory resources of mobile devices are very limited, and the private memory allocated for each app process is also limited. On the one hand we have to apply the memory usage reasonably, lest cause the frequent GC (garbage collection mechanism) to affect the performance and the large object request to have the memory overflow; On the other hand, we should release the memory in time to avoid the memory leak.

Electricity

The battery power of mobile devices is very limited relative to PCs, and maintaining lasting endurance is particularly important. In addition, many of the features of Android are more power consumption (such as screen, gps,sensor sensor, wake-up mechanism, CPU, networking, etc.), we have to carefully check the app's power usage, so as to avoid the user's mobile phone power consumption, resulting in bad experience.

　　

Flow

The current network type contains 2g\3g\4g\wifi, which is differentiated by different operators, we often encounter large resources in the use of the app, repeat requests, call response slow, call failure, and so on. Under different network types, we need to not only control traffic usage, but also speed up the response of the request. In addition, for the need of the network of hand travel, some games for different networking mode of the types of networks using a different flow consumption strategy, mainly divided into WiFi environment and cellular network environment. So for different games, when we count traffic consumption, we may have to connect different networks for testing.

For mobile app test, compared to app compatibility test, App function test, performance test is more test application on the terminal hardware, but the performance test is not separate, often with other special tests to cooperate with the test.