What is the whole process of specific functions, automation, and performance in the middle of work? In fact, the process of software testing starts with getting the requirements. Let's take a look
1. Demand review
First of all, we will go to a demand review meeting. What is the review?
The general reference is the product manual, given by the product manager. The product manager, testing, development and other relevant personnel in charge of this project participate in the requirements review meeting and conduct a series of reviews based on the product requirements. The main two points are as follows:
1. Review whether the requirements on the product specification can be realized
2. Test the functions written according to the requirements, and review whether they meet the requirements of users
After the review meeting, the product managers determine the project practices, develop and test the modules they are responsible for. As follows:
(flow chart)
Second, the test manager assigns tasks
What the test plan includes
product description
Test Range
testing strategy
test target
test period
Resource allocation
Risk Analysis
testing strategy
What kind of tests do we need to conduct for the entire product, that is, whether we only test its functions or both functions and performances.
After the testing strategy is determined, the corresponding person in charge will be assigned, who is responsible for the function, and who is responsible for the performance. If there are not enough personnel, some processing will be done in the emergency risk analysis.
test target
The test goal mentioned here refers to the termination goal, that is, to what extent the test goes. Different types of tests have different termination goals.
Functional tests such as:
1. The coverage rate of test cases should reach 98%
2. Test cases are subject to review
3. All test cases must be executed
4. Remaining bugs should not exceed 5% of the total bugs, and there should be no A, B, or C bugs
When this goal is achieved, we will test until this version. Different companies have different test goals. The specific test goals can be based on the company's specified test goals, and then we can enter the next link.
test period
The total test time starts from xxx - ends at xxx.
How many versions are expected to be tested are related to the version released by development, for example: "Official version V01V02V03V04, regression version, emergency version..."
These are also the contents of the test cycle. Of course, this is just an estimate. The actual situation may be slightly different from the arrangement, depending on the actual situation.
Test process mind map
Software testing process
Development test release version process
Summary of software testing process
1. Demand review
2. The test manager assigns tasks
3. Write test cases and use case review
4. Development and testing, the last class of testing
5. Test Execution Activities
6. Test evaluation, launch
The above is the working process and daily work of a software testing engineer, which is mainly presented in the form of a mind map, which is convenient for viewing and understanding.
Finally: The complete software testing video learning tutorial below has been sorted out and uploaded. Friends can get these For [software testing] friends, it should be the most comprehensive and complete preparation warehouse. This warehouse is also Accompany tens of thousands of test engineers to go through the most difficult journey, and hope to help you too!【保证100%免费】
Software Testing Interview Documentation
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.
How to obtain interview documents:
