App common crash causes and test methods collation

People who have tested apps should find that app crashes are a very common problem and often deadly, which requires testers to do their best to find bugs in the software and reduce the likelihood of app crashes. Here I will collect the information about the app crash test and my work experience as follows:

First, the direct impact of the bug in the app: The app bug will directly affect the user experience, App Store ratings, user loyalty, reputation, etc...

Second, the app crash is a very common type of bug, for example, many times we are using an Android app, is using a sudden application to stop responding, the interface pop-up "forced off error" window needs to force the closure of the app, and the iOS app is a lot of use will be flash back phenomenon, These problems, I think, are encountered by many people, these are the app's common crashes. Because now the market is andriod mobile phone fragmentation, causing the andriod mobile phone more prone to the crash of the app, usually in the network anomaly when the app is still on the data interaction, there will be a crash, possible reasons for many, there may be some extra space in the code, the programmer of the code is poorly handled, No exception handling, and so on, and iOS common app crashes are mostly in the form of flash, these anomalies in the worst case, not only affect the use of the app may also cause system failure, the operating system crashes, the entire app cannot continue to use, the user has to uninstall the app.

Third, the test of the app and web-side software testing compared to the increased complexity:

A, operating system: a large number of devices, various operating systems, currently using the most operating systems are: Android, IOS, Windows, BlackBerry, and so on, the application software between them are incompatible.

B, Equipment: Touch and non-touch devices, limited memory capacity, battery power consumption, screen size, resolution and so on.

C, Network: Different networks and operators, the current China's three major operators have telecommunications, unicom and mobile, different network formats, such as GSM, CDMA, 3G, etc., in the case of bad or no network app behavior.

D, Usability: direction, touch, zoom, paging and navigation limitations, various distractions such as incoming calls, incoming SMS, alarms, and low battery alarms.

Four, the cause of the common crash of the app:

Device fragmentation: Apps may behave differently on different devices due to the diversity of devices.

　　Bandwidth throttling: A network with poor bandwidth may not have enough fast response time for apps.
Network changes: Switching between different networks can affect the stability of the app.
Memory Management: Low available memory, or use of an unauthorized memory location may cause the app to fail.
Too many users: too many connections can cause the app to crash.
Code error: A new feature that has not been tested may cause the app to fail in a production environment.
Third-party services: Ads or pop-up screens may cause the app to crash.

V. App crash test case design:
1 Verify app behavior on multiple devices with different screen resolutions, operating systems and operators.
2 Verify the app's behavior with the newly released operating system version.
3 Verify app behavior in environments such as tunnels, elevators, etc. that suddenly change the quality of the network.
4 change from cellular to Wi-Fi via manual network, or in turn, verify app behavior.
5 Verify app behavior in a network-free environment.
6 app behavior when verifying incoming/SMS and device-specific alerts, such as alerts and notifications.
7 Verify app behavior by changing the direction of the device in different view modes.
8 Verify the app behavior when the device is low on memory.
9 Verify app behavior by applying loads with test tools.
10 Verify app behavior in different supported languages.
Obviously, there will be more app-specific scenarios that cause the app to crash.

App common crash causes and test methods collation