APP stability test
The right to ensure the basic functions on the basis of the stability of APP is particularly important if a card or APP application flash back often to die, poor user experience, in the presence of competing products, it is easy matinee churn.
Stability problems, by black box testing, the gradation measured, and user feedback to find modified.
Gradation beta: beta refers without limitation. But still limit the user's identity, that only eligible users can get beta software.
Then the general and final test, and then is a public beta.
APP testing process:
Project approval: what content is a brief introduction to the project?
Needs assessment: development, testing, and products.
Demand analysis: write test cases
Test assessment: general test team to participate, whether test point coverage in place, whether steps miscellaneous, Prerequisites description is clear.
Implementation of test cases: The project occupies the longest time, maintenance use cases.
Write a single bug: Submit bug.
Regression testing, submit bug tracking and management.
to sum up
1. Requirements Review
① fully understand the needs and lay the foundation for the subsequent preparation of test cases.
② based on an understanding of the needs of the details can be more prepared to evaluate the test points and workload.
③ Local demand ambiguity found, generate a pre defects.
2. How to effectively carry out the needs assessment?
Review the organizers before the review meeting was held ahead of the requirements document issued to relevant personnel in pre-trial review, mobile phone pre-review comments before the official start.
Review the issue in the review meeting for the review more fully and effectively.
3. The part of the test
1. Example of use No. (ID)
2. The use case of the title, abstract (Summary)
3. Preconditions: This example with the implementation of the pre-conditions which need or what conditions will have the expected results.
4. Test step (step)
5. Expected results (expection)
6. The actual results (Results)
7. Priority
8. Remarks
9. Version: Software Version
10 platform
4. Test results of several classification
pass: by
fail: Failed
na: ① ② useless functions described embodiments without tools or execution environment in which to use cases.
block: jam, for example: because they can not log in, so you can not enter the personal center.