Shulou(Shulou.com)06/02 Report--

This article introduces the relevant knowledge of "what are the indicators of Android performance testing?". In the operation of actual cases, many people will encounter such a dilemma. Next, let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

In the process of performance testing, some problems can directly lead to the user's utilization and unloading rate of the current app. If the app is stuttered seriously or the loading page is slow, and the cpu occupancy rate is high, resulting in app flicker and other problems, in the testing process, special attention should be paid to the performance experience. Good app performance, beautiful ui design, clear function level and less path level can improve the user's utilization of app. The issues of concern in performance testing are as follows:

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

2. Flicker: when you click on a certain function point, the customer's heart collapses.

3. Catton, black and white screen:

4. Collapse: (excellent: 0.2%, standard: 20.4%, slight hidden danger: 42.12%, serious hidden danger: more than 12%) often manifested as crash.

5. Network hijacking

6. Poor interaction performance: (excellent: 0~300ms, standard: 300ms~400ms, minor hidden trouble: 400ms~1000ms, serious hidden danger: above 1000ms) phone message interference, low power supply

Wake up, push reminder, usb cable plug reminder, charging reminder

7. Cpu utilization: recommended value > 90% too high CPU frequency setting will lead to overheating, resulting in more serious power consumption, too low cpu frequency setting will lead to mobile phone lag, slow application processing will also lead to power consumption.

Just to avoid being unloaded.

8. Memory leak: this means that you apply for a piece of memory with malloc or new, but do 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: above 5000ms), the application sends a HTTP, please

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

The interface is jammed, at the same time the error prompt, the user experience is very poor.

11. Traffic occupancy: average flow per second, recommended value

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.