Mobile application quality standards
The mobile application quality standard consists of thirty-five test indicators that cover almost all dimensions of the mobile application test. Through the testing of these indicators, the quality of the application can be well covered, depending on the test point, Divided into seven dimensions:
Basic function test indicators
| Basic function test | description |
| basic skills | Whether the mobile application contains the basic functionality is normal |
| Abnormal test | All abnormal operations and complex user scenarios are tested. Including client operation exception, client and server-side interaction exception, network anomaly, interruption, etc. |
| Account login | Check whether the account-related functions are normal. Such as support for different accounts (QQ, microblogging, etc.) function is normal; multiple accounts at the same time login function is normal; multi-login function is normal |
| Package name, version number, signature | Package name, version number, signature is correct |
| Static code scanning | Check the errors in the code using the scan tool and process and explain them item by item |
Performance stability test index
| Performance stability test | description |
|---|
| Power consumption | Power consumption in typical scenarios and in standby mode |
| Traffic consumption | Typical user scenarios and standby traffic consumption |
| CPU usage | CPU usage during typical user scenarios and standby |
| Memory consumption | Typical user scenarios and memory consumption when inactive |
| Start time | All kinds of startup mode, the start time (cold start (boot the first time after the start), hot start, the first start time, start from the recent visit) |
| Content load length | The main page or function is loaded for a long time |
| Exit time long | In the product exit or enter the background operation of the length (back key to exit, home key to exit) |
| Frame rate | Main interface sliding fluency |
| Install the package size | Before installation, after installation, the size of the application after the first start |
| Monkey test | Each iteration must pass at least 8h uninterrupted Monkey test |
Compatibility test indicators
| Compatibility testing | description |
|---|
| ROM compatible | Compatibility with different ROM versions (native ROM (4.0, 4.1, 4.2, etc.); third party ROM (millet, soft valley OS OS) |
| Chip compatible | Compatibility with different chips (MTK platform, Qualcomm platform, Intel X86 platform, etc.) |
| Screen compatible | Compatibility for different screen resolutions（HVGA、VGA、WVGA、FWVGA、720p、1080p） |
| Mobile phone brand compatible | Compatible with different mobile phone brand models (Samsung, LG, Huawei, etc.) |
| Security software compatible | On the security class software compatibility, after the installation of security software will not report the application of the error (such as soft valley phone housekeeper, QQ mobile phone housekeeper, etc.) |
| Version compatible | The new version needs to be compatible with previous versions |
| SDK compatible | Compatible with integrated SDK within the application |
Safety test indicators
| Safety test | description |
|---|
| Configure security | Check the configuration security in a specific scenario, including the release status check, permission application, custom permission, signature validity check |
| Data Security | Check the data security in a specific scenario, including storage security, transport security, log information disclosure, intent information disclosure, key management |
| Component security | Check the security of components in specific scenarios, including activities for component security, services component security, content providers component security, broadcast receivers component security, dynamic registration receivers component security |
| Webview component security | Check the webview component security in a specific scenario, including: addJavaScriptInterface command execution, JS local file theft vulnerability |
| crash hidden danger | Check whether there are crash hidden in the APP, including the input test, check the security of the input in a specific scenario, such as SQL injection, path traversal, IPC empty reference exception DOS, intent injection; interface check |
Traverse the test indicators
| Traverse the test | description |
|---|
| Traverse the test | Simulate the user's actual operation of the application, automatically on the application of each interface can be manipulated elements of the click, record the operation of the path and the problem (screenshot, log) |
Online quality control indicators
| Online quality control | description |
|---|
| customer feedback | Collect different channel user feedback issues and process them |
| Data statistics | Core user indicators, the user allows the case, understand the user to use the product to help improve product quality |
| crash monitor | Monitor the user in the use of the crash situation |
| Shelves monitoring | Check and monitor third-party store shelves, including but not limited to version number, channel correspondence, etc. |
