The main content of this article, reproduced from Http://www.51testing.com/html/04/344504-849373.html,
Here, the main point is to tidy up the overall idea of app testing, where the app does not include Web apps based on HTML5 development.
A new test project, the first to be familiar with the whole process of the project, the general operation of the framework over a piece, carefully study the development of spec, do not understand the place in time to record, summary and development communication.
Think about the main functions of the product and the user group, what are the same types of products on the market today? If possible, use the same kind of app on the market before testing.
This is the first step in testing.
After the product process is clear, in the control of the needs of the app development documents, prepare the first draft of the test plan, considering the application version of a lot, test cases do not have to write too detailed, list the main module function points, roughly what method to test, first marked out, listed to a checklist
For the mobile app test points, can be divided into the following aspects, functional testing (process testing, functional point testing), compatibility testing, cross-testing, installation and upgrade uninstall test, stress testing and so on.
1. Functional testing, mainly to the specific function point one by one test, to ensure that each point can be correctly implemented the corresponding function
Specific recommendations according to the module to divide, not heavy does not leak.
Technorati Tags: testing
2. Compatibility test: To perform testing on the mainstream device installation application in the market, to ensure that it will work properly, we recommend the third-party compatibility test platform, and recommend the Testin platform.
3. Cross-Test: for running applications, if you encounter SMS phone interference, USB plug-in reminders, charging reminders, low battery alerts, and so on, to see if the application can work properly.
4. Install the upgrade Uninstall test: Make sure the app is properly installed, uninstalled, and upgraded.
Verify that the app is properly installed, running, uninstalled, and using the system resources before and after the operation and operation.
Mainly include:
1) Check whether the software can be installed, run, uninstall correctly;
2) Install, uninstall, update error report;
3) Other ancillary information:
is the location and folder reasonable?
Whether the component is registered or deleted correctly;
5. Stress testing: Large user volume, interactive applications need to perform stress testing on the network interface, to ensure that the application in the case of large user capacity to operate normally.
1. Verify that the app responds correctly at various boundary pressures such as battery, storage, speed, and so on.
2. Responsiveness Test: Test whether the various operations in the app meet user response time requirements
3. Stress test: If the system resources are in an abnormal condition under repeated/prolonged operation.
6. Ease of use: the interface is attractive, easy to understand, the overall interface neat, unified, no typos, text, pictures are good, the operation is friendly.
If the tester believes that there is an unreasonable place, you can raise the bug.
For testers or user feedback problems, the need for a dedicated tester to consolidate, fill in the Bug tracking system for tracking processing. For some more serious crash or can not reproduce the problem, need to add automatic feedback in the software crash log mechanism, write their own or use the third fangyou the application of statistics are all right. In the application upgrade maintenance, log log analysis is critical.
Regression testing after a bug fix, a full-quantity use case regression test before delivery.
Android App Test Essentials