Mobile App Test Framework

When you get a new app, you'll start by classifying him first. Broadly divided into: UI, functionality, compatibility, security, user experience, exceptions, business scenarios, interfaces, performance and so on. And then we'll introduce them one by one.

UI Test:

According to the UI design diagram or prototype demo, check each individually.

Functional testing:

The first is to ensure that the functionality developed meets the requirements in the requirements documentation.

Another is the app common test rules, roughly divided into the following categories:

1. about the app installation:
   • has never been installed in the software phone to install properly.
   • is installed, if the installation is normal overwrite, and so on.
   • The installation is normal after uninstalling.
   • the file path and file are correct after installation.
2. about app Startup:
   • After the installation is complete, the app can start normally
   • kill the process, the app can start again
   • launch app content
   • Check user initialization information after startup
   • Whether you need to rely on network for startup
3. about app Upgrade:
   • After the new version is released, can you monitor the automatic upgrade
   • upgrade to the correct version, overwrite the old version, and start using
   • can support skip
   • Level
   • upgrade, if a network outage occurs, after the upgrade is continued or re-downloaded
   • after the upgrade succeeds, user data and settings are retained
   • do not upgrade, the app can use
4. About the app uninstall:
   • after uninstalling, whether the installation directory cleans up
   • If there is user data after uninstalling the reinstallation
5. phone Memory:
   • When the phone is out of memory, can support an Install or upgrade the
   • app to support installation to an external SD card
6. program interrupt:
   • network interrupt
   • call interruption
   • lock screen Interrupt: Stay in the program Interface to lock screen, after recovery check whether the operation is normal
   • load interrupt: Page interface request, interface frame loading, through the home key, return key, fast switching operation to interrupt
   • before and after the switch: stay in the program operator interface, through the home button, To switch between the front and back of the program
7. Phone Universal key:

Mainly reflected in the phone's return key operation, whether to return to the previous page

1. Mobile System Configuration:
   • Process management: Power-saving management, background process residency management
   • Display Management: Font size, font type
   • Language environment
   • Screen configuration: Whether to support the adaptive processing of the screen
2. Flow:
   • Whether the app traffic meets expectations for the first time, and when it's in use, is to call the local cache or retrieve it from the server again
   • Does the image size and size of the app account for the impact on network traffic?
3. System permissions:

Such as: Network permissions by the butler, the system security software restrictions such as networking operations.

Privilege sensitivity, such as address Book, is carefully acquired for the system's top secret privileges.

Compatibility test:

Contains: Strong if the network environment, different network operators, mobile phone screen resolution screen size, ios/android/windows operating system phone, may also involve operating system version of the different

Security testing:

1. Whether the request parameters have been encrypted (e.g., can be checked using the fiddler, Charles, etc. grab Kit tool)
2. Do not expose URLs when error pages
3. Not identified by mobile security software as a virus, etc.

User experience:

For example: whether the information is friendly, the key position is reasonable

Exception or Business scenario:

This is based on the business needs of our products to consider some unusual case or the operation of the occurrence.

Interface test:

If an interface test session is required, the interface document is first compiled by Rd and the interface is tested.

Performance test:

Two kinds, one is the performance of the phone, the other is the performance of the server.

Mobile phone performance monitoring: Mobile phone CPU, memory, power consumption, etc.

Server performance is more concerned about the service side CPU, memory, response time of the request, and how many concurrent users can be supported.

The above listed content, if there is not comprehensive place, welcome to add.

In addition: No matter what test, the premise must first with the problem, follow-up to find more problems.

Mobile App Test Framework