App Flash analysis and crash log capture

Now people are increasingly inseparable from mobile phones, mobile phones are already part of our lives. Apps are becoming more and more, to make their apps stand out, to be able to have a place in the mobile internet era, in addition to meeting the needs of most users, but also to make their app experience the best. So app Flash may lead to user churn, so as research and development, testers should minimize the crash rate of apps. Therefore, in the process of testing also pay special attention to the flash back.

Say so much, so especially for testers, how to encounter crash (or occasional) should do? You have to grab the logs, and here's an example of Android:

First, after the phone crash, if the pop-up "application stops unexpectedly" prompt if not disappear, you can use the following methods to get the crash log

1, directly connected to eclipse in the DDMS for Crashlog access.

2. Or by command: ADB logcat–v time >e:\x.txt (the meaning of-V is: The log can be printed to see the specific times).

Second, after the mobile phone crash, if the pop-up "app stops unexpectedly" prompt if disappear, get the method of crash log

1. ADB bugreport >e:\xx.txt

2, the log will be saved to the appropriate directory, open the log file search keyword "Fatal exception" or "Crash" to find the corresponding crash log.

App Flash analysis and crash log capture