Special

Introduction: For the current series of outstanding problems finishing discover types of problems is always likely to be a long time Tucao user on the formation of the hardest hit is particularly important for the analysis focused on the hardest hit.

1, the collapse of class issues (anr the main thread load> 5s Java crash native crash)

2, under certain scenarios easily Caton (out of frame cpu issues)

3, the corresponding user response is too slow during use (cold start scenario complex interaction page load H5)

4, fever (hardware)

5, compatibility (model)

...

After classification for the reaction of the hardest hit by the user basically fall into several categories: crash tests (monkey or customized depth traversal) app performance webview performance analysis Caton memory test compatibility test (appium gird), etc.

A crash test, you can traverse the depth information to supplement error logcat monitoring system during automated testing real-time reporting

adb logcat *:S *:E | grep AndroidRuntime

508 adb logcat | grep -i displayed # find which applications start at Home

adb shell ps | grep xxx.xxx.xx find the process ID

512 adb logcat | grep 9744 | grep *: E Error Message filtering process
520 adb shell monkey -p com.xueqiu.android -v 5000

 

two,

 

Guess you like

Origin www.cnblogs.com/1026164853qqcom/p/11402953.html