a
, Exception Scenario summary
Mobile testing is a lot different from back-end web-side testing, for example, logically, it may not be as complex as the background, but the scene is varied by platform diversity. Here are some special scenarios to consider when moving a test:
1. Network Conditions
Network testing is a common test scenario, but it is easy for us to overlook, because the test is generally faster in the network, but the problem of user experience caused by networking problems is the most. So the test in the network situation, is necessary, can be divided into three kinds of situations:
- Good network
- Bad network, generally refers to the downward speed of about 10k, naming "Weak network"
- Network environment switching (from good to weak, from weak to good)
Test tool: Charles
2. Interrupt Testing
Interrupt testing is one of the differences between mobile-side testing and web-side testing, and regardless of whether our app features are implemented using native or H5, this scenario is something to be aware of. Interrupt testing includes, but is not limited to, the following:
- Phone, SMS Interrupt
- Home key toggle, or front and rear switch
- Message notifications, push interrupts
- Power interruption, Bluetooth interrupt, alarm interrupt, Plug and draw data cable, mobile phone lock screen
3. Safety-related
Electronic contract project has the function of sending SMS, but there is no limit to the number of messages issued, there is the risk of malicious multiple triggering. So you need to be more aware of these security issues when testing your app.
Security testing can be divided into rights control, data security, security vulnerabilities and so on.
- Permission control: Need to pay attention to the phone memory, photo albums, cameras, positioning and other common functions of the rights control, when prohibited, switch, whether it can ensure the normal use of functions.
- Data security: Now take the token encryption and key information such as password MD5 encryption means to ensure the security of data, but there are many aspects of app security testing, there is no very good special test in the group.
- Security vulnerabilities: For example, the above example of the text messaging function, now can only be based on the functional level, as far as possible in the design phase to consider and avoid these problems. Security vulnerability can be hid with Wed end H5 page Communication security, local security (refers to the client's local environment and data security, and code to solve the security problems caused by the problem, such as: plaintext storage problems, malicious two packaging problems, ultra vires operation issues, etc.)
second, the
matters needing attention
In addition to the three aspects mentioned above, there is still a lot to be done in the work, to avoid encountering or missing tests in the future:
- Clears the app's usage after applying the cache, including whether the cached file was successfully loaded again, and so on.
- The coexistence of apps and other mobile applications, should be compatible with some of the more commonly used mobile phone applications, such as social software QQ, input method software Sogou news fly Baidu
- Jump problem: The test process will always encounter different scenarios need to enter different pages, including the use of Android physical return keys, it is recommended that this jump problem in the requirements of the development, according to user needs to develop, otherwise all follow the default rules to return to the previous page, in the testing process need to focus on the page jump and return problems.
- Special models: Huawei. The Rom of Huawei mobile phone often has a lot of problems when it is adapted, and can pay more attention when testing.
Mobile End Test Summary
