1.1 Common research and development process for Internet products
First, we need to introduce an Internet product development related Division of labor
1, Product manager, responsible for product direction and specific requirements of the planning, need to write the document.
2, Project Manager (PM), responsible for project planning and scheduling, and follow-up project development progress, change and risk, as well as a variety of cross-team coordination work.
3, designers, responsible for product interaction design, visual design and other aspects
4, research and development personnel, responsible for product technical framework design and code compilation, output is the actual product can be run
5, the test personnel, responsible for product quality control, including the function, performance and stability and other aspects of the test content.
6. Operation and maintenance personnel.
7. Operation Personnel.
From the point of view of testers, the value of requirements review is mainly in the following aspects
1. Fully understand the requirements and lay the groundwork for subsequent test case writing
2, based on the requirements of the details of the understanding, you can more accurately assess the test points and workload
3. Identify areas of ambiguity in demand.
1.2 Test case design and review
Whether to write recommendations on use cases:
1. Investment in use case design.
2, the use case to write the level of detail. The test case should include at least the following features:
A. Topics of use cases
B. Test steps
C. Pre-conditions
D. Test data
E. Expected test results
A use case is a synopsis of a story that requires a corresponding tester to understand the context of the requirement and the underlying implementation.
3. Form of expression
Common Xmind, Freemind and other tools. "Software Testing", Paul C.jorgensen, "Software testing by Microsoft", "Exploratory software Testing"
1.3 Test Progress Management
1. Test progress Report: issued in the middle of the test phase, to inform the progress of the test work, identified problems, risks, and the following plan.
Risks and issues, test work progress, current bug stats, bug list not closed.
2. Test Completion Report: The end of the mark test work, will give the corresponding test results and conclusions, including whether to meet the published standards and the remaining problems.
3, the systematic method
In the completeness and efficiency of information to further enhance the space, the main problem is reflected in the following aspects:
- The information in the report is written by hand.
- Some time dimension information is lost
- The cost of communication
The information of the functional test platform is roughly said to require a system from three aspects
- Version Requirements Management Platform
- Test Case Management Platform
- Defect Management Platform
Mobile App Testing the 1th Chapter product function Test overview