Some key points of mobile APP test case design

1. Start and stop of the application

.

Whether the welcome interface appears at the first start, the stay time of the welcome interface is reasonable, and whether the application is normally entered after the welcome interface; whether the
first startup time is reasonable; whether
the pulled information is correct; whether the

second startup is consistent with the

startup time Expectation;
whether the application can be entered normally from each startup entry: the main icon of the program startup, the shortcut key of a certain function, the widget;
the status check after startup: such as initialization information, initial status,
startup : process name, Number of processes, service name, number of services, SDKs called by third parties, such as GPS
applications with login, whether the login is normal when the application is launched for the second time. Start after the

program exits abnormally. Start after the

operation crashes: such as null pointer, memory overflow, etc.
Manual stop Process: In the case of multiple processes, stop all or stop one of them and then restart.
Manually stop the service: In the case of multiple services, after stopping all or some services, use it directly without restarting
.
Clean up software data

2. Program function module     

This is generally to verify the trigger events of all functions of all modules of the application one by one according to the requirements. This is the most basic to be examined from two aspects. On the one hand, the module is operated in compliance with the requirements, and whether the expectations specified by the requirements are met; Uncle Liao proposed the concept of test modeling that Google is using. This method can help us better combine the architecture of the requirements analysis application and design more complete functional module use cases.

Text box input function

Normal input, input out-of-bounds, special character set (\n, \r, etc.), use copy and paste to input content to the text, the input program stipulates that the input character

event triggers

whether each button and each clickable item can meet the requirements Specified function
Try to click the unclickable area on the page to verify whether the reserved test backdoor is closed during the test process.

3. Permission security Permissions that

require user confirmation are not authorized, and the permissions are closed by default.
Network permissions are restricted by housekeepers and system security software.
Permission sensitivity, such as address book, are carefully obtained for top-secret permissions of the system
Use security software to scan for security loopholes and viruses to see if the tested APP will be prompted by these security software to have problems and affect the user's perception of the tested APP

4.

Temporary file storage path and naming method generated during the use of the APP
. File storage method generated by the download operation involved in the APP. The
stored files are locked and occupied
. Both external SD and built-in SD cards are required. Check whether the files generated by the APP are correct. The
APP is installed on the SD card or the storage space of the mobile phone. The
disk space is insufficient, and the disk has no permissions (such as read and write).

5 Network and traffic

Network signal, especially the performance of the application in weak network environment
Different operator networks : Telecom, China Unicom, China Mobile, 2G/3G/4G
network interruption, logical processing of network recovery scenarios (such as retry), and network prompts Whether the traffic of the
first application startup meets expectations
The impact of statistics and abnormal reporting on traffic is the
size of pictures in the APP , Whether the size has considered the impact on network traffic
Special services based on traffic security, such as Wi-Fi-only Networking

TestBird