What are the process specifications of software testing? How to do it?

Catalog

1. The goal is

2. All stages of the project

---

1. The goal is

This paper is mainly to standardize the test process in the project , It mainly assigns the respective functions of the development group and the test group in the project , And in the project , Responsibilities of each group .

2. All stages of the project

The project is mainly divided into 9 Stages , Namely ： project , Requirements analysis definition , System 、 The structure design , Detailed or programming , code , unit testing , A functional test , The system test , The acceptance test . The definition of project establishment and demand analysis is to need customers , market , Product personnel to confirm , System 、 Result design , Detailed or programming , Coding requires engineers , Technical personnel carry out technical realization , unit testing , A functional test , System testing is implemented by testers . The acceptance test is completed by the tester together with the customer . But because the company needs , Now some tests can only be completed by the development team . Specific groups should perform their duties at each stage as follows ：

                   

1. Proposal stage ：

The project establishment will be negotiated by the customer and the product salesperson according to the market demand , Determine a general software design direction , It's mainly about what kind of product you want to complete , The main function , For users . And determine the requirements , Clarify project functions

2. Demand analysis stage ：

The technical department and product personnel analyze the needs , Analyze each function point one by one , Including what data to input , What results to get , What should be output in the end . Describe the purpose of the software in detail 、 Range 、 All the work to be done to define and function . And the completed requirements and requirements analysis are handed over to the test team , The test team began to be familiar with the overall operation process and function points of the project .

When the requirements change in the later software design and coding, the project manager needs to update the requirements in time , And clearly mark out the changed needs , And deliver it to the test team .

3. System 、 Structural design stage （ Mainly including interface 、 modular 、 database ）：

The development team has entered the development stage , Implement the system construction design and structure design of products , At this time, the project manager needs to sort out a design outline of the product , And hand it over to the test team , Help the test team understand the design concept of the software in detail , At this stage of testing, you can put forward some views on software design , Or put forward operation habits from the perspective of users .

4. Detailed or programming stage （ It mainly includes the methods of realizing functions 、 Interaction between data ）：

The development team has entered the detailed design stage of the software , This stage is mainly about the system structure of the development team , Design of data interaction , The project manager also needs to provide detailed documentation , And help testers get familiar with the structure of the software .

5. Encoding phase

The development team officially started writing code , The code should be written strictly according to the requirements and function points . The test group writes the use cases , At the same time, use cases should be written according to requirements and requirements analysis . If in the coding phase , In case of requirements change , The development team needs to communicate with the test team in time , And provide the latest requirements to the test team .

After the test group completes the writing of use cases , You need to provide a use case to the project manager , And review the test cases with the project manager . After the test case review , The test team confirms the test scope with the project manager , Test start time , The project manager is required to provide testing technical support , Test the scale and write the test plan . And evaluate the test time with the project manager , Priority of each sector , Risk management, etc .

                       

6. Unit test phase

After coding , Enter the unit testing stage , This stage is mainly tested interactively by developers , Supervised by the project manager , It is necessary to strictly test one module by one , And make relevant records , After defects are found, they need to be collected and sorted out by the project manager , And assign developers to modify , Testers conduct cooperative testing on the development .

After defect modification , Similarly, conduct interactive verification and make relevant records , Indicate the defect modification , At the same time, record the findings 、 modify 、 The name of the verifier , For later tracking defects .

It is suggested that the verifier and the person who found the defect should be the same , This can better verify defects . For all defects, it is recommended to use BUG Management tools , for example BugFree, Zen and other management tools

7. Functional test phase

Mainly test group , Complete the function test with the cooperation of developers , And make relevant records , When a defect is found , Record in detail the version of defects found , The current test environment , Steps to discover defects . And urge developers to BUG Make changes .

In acceptance BUG when , Verification records also need to be made , Mark the defect destination .

8. System test phase

The test team tests the software systematically with the cooperation of developers , Use the software strictly according to the requirements and the actual environment , When a defect is found , Record in detail , During verification, it is necessary to mark the defect modification status . And views and suggestions on software .

After the system test , The test team needs to write a software risk assessment report , With the overall evaluation of the use of software

9. Acceptance stage

The test team cooperates with the customer to conduct acceptance test of the software , And record the problems found in the acceptance test and the views of customers on the software .

After the acceptance test is passed , Testers need to pay attention to the time-consuming when writing test reports 、 human resources 、 Number of defects found 、 Number of defects severity 、 It takes time to fix every defect , Test requirement coverage , Overall evaluation and modification suggestions from the perspective of users .