Several key steps of software testing, you need to know

Remember 2 When I first graduated years ago, I heard about the software testing industry , At that time, I also went to Baidu to search carefully , The evaluation is basically stereotyped .

The reason for optimism is , Experts believe that user experience will be paramount in the future Internet market , And product quality is closely related to user experience , Since the post of product manager became popular in recent years , The concept that everyone is a product manager is deeply rooted in the hearts of the people , But in fact, everyone should also have the concept of quality , Excellent product quality can provide a better user experience . But there are several key steps in software testing , You know what? ？

One 、 The goal is
Develop a complete and specific test route and process , For quick 、 Efficient and high-quality software testing provides the basic process framework . The ultimate goal is to realize the standardization of software testing 、 Standardization .

Two 、 Test flow description

3、 ... and 、 Demand analysis

Demand analysis is conducted by SA To develop , It is required to refine the details of each function , The position and boundary range of each button , Modeling is required for slightly larger or more complex requirements .

（1） Test requirements are the basic basis for making test plans , Only the determined test requirements can provide an objective basis for the test plan ;

（2） Test requirements are the guide for designing test cases , Only when you have determined what to measure 、 What needs to be tested , In order to design targeted test cases ;

（3） Test requirements are the denominator for calculating test coverage , Test coverage cannot be effectively performed without test requirements .

Four 、 Requirements review （ Need clarification ）

Participants , Include ：SE、OM、PC、AD、TE as well as QA.

SE Put forward requirements .

Developer （OM、PC、AD） Consider the scheme and feasibility of function realization .

TE It is mainly to ask questions about the understanding of requirements , In order to write use cases according to requirements .

QA People are the people who ultimately verify software quality , So you also need to understand the needs .

5、 ... and 、 Developers write scheduling

Developers need to schedule according to the required function points , Then send the development plan to all people involved in the project .

6、 ... and 、 Test plan scheduling

Testers according to the development plan , Schedule the specific test time （ Include SIT Transfer measurement ）, Then send the test plan to all personnel involved in the project .

7、 ... and 、 Write test cases

According to the detailed requirements document , Start writing use cases .

8、 ... and 、 Use case review

Before use case review , Send the use case to relevant personnel first , So that they can know in advance which functions will be verified by the use case and the details of the verification .

In use case review , Participants need to put forward modification suggestions for use cases that do not conform to the actual functions or use cases with non-standard format .

Nine 、 Submit baseline

After the developer completes all the functions , Will conduct a self-test on their own functions . After the self-test is completed, submit the test for baseline .

Ten 、Showcase

After the self-test is completed, the developer will demonstrate the realized functions to the tester .

Testers can ask questions, which can be answered by developers or solved later .

11、 ... and 、 Transfer measurement

Transition testing is the development of all requirements , And all the requirements are showcase complete .

（ namely ： The system test before the development is transferred to the test team , The purpose is to evaluate whether the functionality of this version is testable . If the prediction test fails , repulse , Development team rework , If you pass , The test team began the first round of system testing .）

Iterative exit （ The iteration exit is before the transfer test , Before the iteration exit is the iteration period ） It's done , You need to go to the test environment to verify .

The test transfer time is determined according to the version . After version transfer test , This version needs to be summarized , The version producer needs to summarize the exceptions during version merging , Record the closing events , Give the responsible topic for the reason of version delay .

(1) The first round of system rotation test , The test group executes all test cases , If defects are found, submit a problem sheet , And report the test progress every day . After the first round of testing , The test team submits all the problem sheet tracking to the developers , It's up to them to modify . Then test the second round after baseline , The second round will focus on the problems found in the first round .

(2) Before they fix bug period , The test team will make a test evaluation for the first round of system test , Make a test report . And according to the actual situation , Modify and add the test cases written by the test group , Development changes bug end , Submit a new version to the test team .

The first is the regression defect , Then some high priority use cases will be selected for testing , If problems are found, continue to submit the defect problem sheet , Until the defect rate is lower than the user's requirements , The test team will conduct the last round of large version testing , End the system test . The specific test rounds are determined according to the version quality and project complexity .

Twelve 、 The test passed

After two to three or four rounds of testing , Until no new problems are found . Or temporarily unable to solve , Or not urgent , Confirm by superior , Can pass .

Prepare test report and acceptance scheme （ The acceptance plan is submitted to QA validated , Testers focus on whether the function can work properly ,QA Focus on the quality of the whole process and the quality of end users ）.

13、 ... and 、 Test evaluation

At the end of the execution phase, enter the test and evaluation phase , The test team will issue a general test report to make a detailed evaluation of the process and version quality of the test team ：

1. Requirements need to be reviewed ？

2. Use cases need to review those ？

3. The plan should review those ？

4. Defect review those ？

5. bug assessment ？

fourteen 、 Test summary document report output

The specific task leader can be asked to evaluate the model speed personally responsible in this test , Put forward relevant suggestions , Give an overall assessment .

bug According to different levels of Statistics , Number of use cases 、 Number of cases executed .

Statistics of testing human resources in the project .（ Company ： people / God ）

Statistics of software and hardware resources in the project .

Put forward the overall evaluation of the software .

15、 ... and 、 Test report

The test report includes the conclusion of the software function , Describe the software capability designed to meet this function and the capability confirmed by one or more tests .

Explain whether the software development of the project has reached the predetermined goal , Whether it can be delivered for use . Summarize the resource consumption data of the test work ： Such as the level and number of staff 、 Machine time consumption, etc .

Record the test results and findings and the bearing body of various outputs obtained from the test work of the project , According to the input and plan 、 Compare the requirements to summarize the experience gained in this project .

sixteen 、 remarks

Test team responsibilities ： Requirements review 、 test plan 、 The test case 、 Test case review 、 The test execution 、 Defect report 、 Defect tracking 、 Test report

Test team deliverables ： test plan 、 The test case 、 Defect report 、 Test report

Source of the article ： The Internet The copyright belongs to the original author

The above is not for commercial purposes , If it involves intellectual property , Please contact Xiaobian , We will deal with it immediately