App Test points Summary (function, interaction, crash-state analysis, error-prone checkpoints)

App Test points Summary (function, interaction, crash-state analysis, error-prone checkpoints)

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

recently involved in app-side testing, the common checkpoints are summarized below: I. Operational aspects:1. Registration (Invalid data culling), login (voice and SMS Verification code), third party login (, Weibo, QQ), forget password processing, registration (identity check after login) Account kick (one account can only be logged on one device at a time) 2.tab toggle, swipe, title display 3. The list of items shows: swipe up or down to load (will not load data repeatedly), display the correct number of bars, format, label is correct; message list display: Title display; Avatar Display processing ; time display rule; drop-down to refresh the latest message, unread message display, marked as read setting 4. Search: Smart tips suggestion; search history (typically duplicate only the most recent search); search limit (some by English characters, the limit of the number of times in one minute); Click X and cancel the difference Search no data Processing 5. Details page: Share the title, the picture, the description to display; To return to the app after sharing; copy, link, required field, time display rules (year, month, day, hour, minute, yesterday, just); sort order 6. Chat page: The first chat content automatically display, input area default text; Whether it is instant; blocking and attention prompt processing; Handling a message that has failed (this scenario is very complex, such as how to set the limit in the middle of sending) 7. Personal Settings page: Avatar Settings (local gallery, mobile phone camera is particularly prone to crash), personal information modification (when the first entry on the change is valid)   Two. Interaction (focus on user experience):1. When the keyboard is tuned, when to close: 2. When there is no network: Network exception prompt for each page (network timeout, No network) 3. Status of each icon: likes, filters, Favorites 4. When to refresh the pull update data (some return no refresh, just re-enter to refresh) 5. Click the Home button or go back to the background to send a message push message (easy to crash when clicked)   three. Common crash-state causes: Functional Aspects:1. Click the Home button or return to the background, send a message push message push after the click easily crash 2. Frequent drop-down refresh Data 3. The Input text box content exceeds the limit or the format does not support 4. Performance: For instant interaction, long time not accepting large amounts of offline message logon Network problems:1. Request network operation when the network is disconnected 2. Request Network operation when networking is poor third-party apps: (call other apps)1. Enter the details page to invoke a third party, such as H5, or to invoke an application that exists when the file is viewed 2. Modify Avatar to call its library or camera crashes 3. Weibo Login (third-party login) 4. Desktop application interference: Call, SMS, power Other questions:iOS: Crash comes from two types of problems: the violation of iOS policy and the killing of its own code bugs. Violation of iOS policy: 1. Low memory flash back 2. Watchdog timeout: When a particular UI event (such as Start, suspend, resume, end) is not responding, watchdog will kill our application 3. User forced to quit Code issues:1. The message notification bar crashes into the message ( TableView. Delegate did not clean up iOS in time) 2. The most common crashes come from code bugs, such as array out-of-bounds, intervening spaces, null references, referencing undefined methods, multithreading security, accessing wild pointers, sending selector, and so on. 3. Identity is not acquired after login, the identity related operation gets empty, crashes 4. Crash on screen toggle: The activity is recreated at the time of the screen and the Activity property configuration is not added 5. Share the crash: May be sharesdk crash, friend League error statistics not captured to crash log, should be SHARESDK and captured reference: iOS end Crash Analysis: http ://www.cnblogs.com/yangxia-test/p/5107502.htmlios Test Point:http://mp.weixin.qq.com/s?__biz=mza4mtcyotewmw==& Mid=2650610662&idx=2&sn=7c4e15d374b6b902f8c1557a1654cf57&scene=4#wechat_redirect

Bo Master: Haining

Contact: [Email protected]

App Test points Summary (function, interaction, crash-state analysis, error-prone checkpoints)