Sorting of indicators concerned in Android performance test

During the performance test, some problems can directly lead to the user's utilization and unloading rate of the current app. If the app is stuck seriously or the page is loaded slowly and the CPU occupancy rate is high, resulting in app flash back and other problems, during the test, special attention should be paid to the performance experience. The app has good performance, beautiful UI design, clear function level and less path level, Can improve users' utilization of app. The problems that can be paid attention to in the performance test are as follows:

1. Connection timeout: the primary concern of app. In mobile applications, the highest proportion of network error data is connection error timeout

2. Flash back: click a function point to flash back, and the customer's heart collapses

3. Caton, black and white screen:

4. Crash: (excellent: 0 ~ 2%%, standard: 2 ~ 4%%, slight hidden danger: 4 ~ 12%%, serious hidden danger: more than 12%%) often shows crash

5. Network hijacking

6. Poor interactivity: (excellent: 0 ~ 300ms, standard: 300ms ~ 400ms, slight hidden danger: 400ms ~ 1000ms, serious hidden danger: more than 1000ms) telephone short message interference and low power lifting

Wake up, push reminder, USB data cable plugging reminder, charging reminder

7. CPU utilization: the recommended value is > 90%. If the CPU frequency is set too high, it will lead to overheating and more serious power consumption. If the CPU frequency is set too low, the mobile phone will lag, and the slow application processing will also lead to power consumption, then it is better

Just avoid being unloaded

8. Memory leak: it means that you applied for a piece of memory with malloc or new, but did not release the memory through free or delete, resulting in the memory being occupied all the time

9. Bad interface: redundant interfaces exist but have not been used

10. Response time: (excellent: 0 ~ 400ms, standard: 400ms ~ 2000ms, minor hidden danger: 2000ms ~ 5000ms, serious hidden danger: more than 5000ms), the application sends an HTTP request

The time taken for the host to return the response can be divided into strong network and weak network. The strong network is not introduced. When the network signal is poor under the weak network, such as in the elevator and on the subway, the app page is loaded in circles

The interface is stuck, with error prompt and poor user experience.

11. Traffic occupancy: average traffic per second, recommended value < 5.12kb, average traffic per 10 minutes, recommended value < 3MB. There are behaviors such as app sneaking traffic. When users see the traffic occupied by app, like you

The app occupies the first place. If the traffic runs outrageously, it is possible to unload decisively

12. Power consumption: the brightness adjusted by the root phone is related to the long-term use of the app. If playing games, the power consumption is higher than that of ordinary apps

13. FPS: FPS is greater than 18 frame ratio, and the recommended value is greater than 90%

The summary is as follows:

1) Timeliness: startup time / operation response time / content loading time

2) Stability: startup / operation / content loading success rate

3) Resource consumption: CPU / memory / traffic

4) Power consumption: running / standby power consumption under different networks

Good indicators of APP performance test:

Fast application startup, timely UI feedback response, smooth list scrolling operation, reasonable memory use, no crash, etc

The above is all the knowledge about Android performance test indicators. Thank you for your learning and support.