|How to analyze bugs? Professional summary and analysis

What does the special test measure ？

Resource class performance test

CPU Occupy

Memory footprint / Memory leak

Low resource and environmental performance

Weak network test

Speed performance test

FPS test

End to end service delay

velocity analysis ： client + The Internet + The server

Stability test

MTTF

Monkey test

Compatibility test

Android edition

The resolution of the

hardware configuration

Apply custom test items

Protocol testing 、 Data redundancy ratio 、 The success rate

How to do special tests ？

1. Requirements review stage

networking

Broken network reconnection , Breakpoint continuation logic

Whether there will be a large flow , Flow rationality （ Whether the traffic consumption is similar to the file size sent ）

request - There are many responses back and forth , Whether it will increase the failure rate

The protocol must have a compression policy

Is there a caching mechanism

UI aspect

There is IO operation , For example, save , Import , export , send out , Upload , Whether there is a loading process when big data is encountered

Element or dynamic / There are too many variables, too complex , Whether it will cause interface jamming and CPU Long term high （ Such as LISTVIEW Complex format or dynamic graph ）

Element loading timing （ For example, when sliding the list , When to load the avatar ）

Electric quantity /CPU aspect

Location related logic , Detection logic （ Such as face recognition 、 Ear test ）,

Background services （ Such as tcp Heartbeat logic ）,

Audio video correlation

OOM aspect （ out of memory ）

Cache policy , Load big data policy

GC Strategy

Compatibility

Newer system features

Through the system API/ Get data from the system database

Hardware related （ camera , Screen touch effect , The sound is loud ,gps）

2. New function stage

principle ： Find the problem first , Give consideration to data precipitation

What you can do in advance ：

The lack of comparative historical data should be supplemented first , Precipitate existing data

use MonkeyRunner Simple automated scripts , It can make the trend of resource monitoring curve more obvious

Test environment preparation ： Such as test number , Mobile phone selection , Pre construction of test data, etc .

The flow index can be measured first

Special problems found , Please direct the bill of lading first

After the function is stable , Pay more attention to FPS, Memory ,CPU etc.

Focus on FPS: Animation effect

for example , List scrolling , Scrolling of display content

Focus on memory ,CPU, Threads ： A repeatable action

for example , Switch accounts , The interface opens and closes

Focus on traffic , Time consuming , The success rate ： Network related operations

for example , Send a message , Send pictures , Download data

Pay attention to electricity /CPU: Continuous action and high-frequency operation of users

for example , Place background , Send heartbeat packets

Focus on speed ： Interface switching , Content loading

for example , Starting speed