How software testers write test reports

I have written about how to write the test plan before ？ How to write test cases ？ therefore , Of course, there are also test reports that play an important role in the test documents , So how did Wang Doudou write the test report today .

How software testers write test plans

How testers design test cases

1、 When to write ？

The test report is usually prepared by the test leader after the completion of the project test or an iteration . If it is not a project , There are only one or two testers , That is written by the project leader , If you are the only one to test , It's up to you to write .

2、 Test report content

The main content of the test report can be roughly divided into test scope 、 Test progress 、 Defect management 、 The test conclusion consists of four parts , In the actual writing process , We can output these four parts or more according to the requirements of the enterprise .
（1） Test range

The test scope is mainly to write the functions that need to be tested in this project or this iteration , Generally speaking, it is mainly based on new functions and modification functions , Supplemented by regression test content , The test scope in the test report can be extracted from the test scope in the test plan , Then supplement according to the functions actually tested in this round of testing activities .

The test scope in the test report is different from that in the test plan ：

1. Content ： The test scope in the test plan is sorted out according to the requirements documents , The test scope in the test report is sorted out based on the actual test content

2. result ： The test scope in the test plan has no test results , The test scope in the test report needs to indicate the test results

Take some functions of wechat circle of friends as an example ：
（2） Test progress

The test progress in the test report consists of two parts ： One is time schedule （ Exhibition ）, The other is the time spent by personnel testing .

1、 Time schedule

The test time in the test report is more than that in the test plan. The actual start time and actual end time in each stage .

I'm an example :

The planned time and actual time of each stage in the above example are not absolute , Nor is it accurate , The estimated time of each stage depends on the amount of test content in this round , The actual time depends on the efficiency of the tester 、 Test content 、 Development quality determines .

2、 The test takes

The output of test time is not in the test plan , The output test time in the test report mainly reflects the total unit labor time spent in this round of testing , It also reflects the software quality of this round from the side .

I'm an example ：

Performed by ：X people （XXX、XXX、XXX etc. ）—》 How many testers participated in this round of test

It takes time ：XXX people / God —》 Total unit manpower time

（3） Defect management

Defect management is the core content of the test report , The test report needs to output the defects of this round of test from different dimensions , The purpose is to get software quality from defect analysis 、 modify bug The efficiency of 、 Development quality, etc .

Output is required in general test report ：

Defect summary

Count all defects in this round , You can summarize according to the test version

I'm an example :

a. Press bug Grade points

according to bug Grade statistics the distribution of defects in this round

b. Divided into modules

According to the test system / Module to count the distribution of defects in this round

c. Defect convergence

The defect convergence is added every day in the statistical test process bug Count 、 solve bug Count 、 close bug Count , To check bug Is the convergence healthy , Generally speaking, the first test version bug The number will increase , Back slowly bug It will reduce , close bug The number will slowly increase , Here we mainly check one bug Number of openings 、 Post test bug Whether the number has increased .

The defect convergence is shown in tables , It can also be displayed in the form of charts , It shows the health degree of defects .

Defect management is not limited to the above contents , It will also include others according to the actual project situation bug Analysis content , Such as defect status 、 Defects left .
（4） Test conclusion

The test conclusion in the test report absolutely accounts for C Bit , There are also enterprises that only need the test conclusion to write the test report .

The test conclusion includes a summary of this round of test process , It is mainly to find out whether the project has reached the online standard after this round of testing , Therefore, the test conclusion has passed the test , Can go online , Or the test fails , It is recommended not to go online .

1、 The test passed , Can go online

Summarize the language and write the dimensions and functions of this round of test / Business testing , Meet the requirements documents and online Standards .

I am a simple example ：

XX The project has carried out functions in the test environment 、 reliability 、 Security 、 Usability 、 Five aspects of performance are comprehensively 、 Strictly 、 Standardized testing , The test results show that ,XX The project has achieved XXX Business , The project test quality meets the requirements and online Standards .

Test conclusion ： adopt

2、 The test failed , It is recommended not to go online

Generally speaking, the software test conclusion rarely includes the failure of the test , But software testers still need to give practical conclusions according to the actual testing situation , If the software quality is not ideal , Don't be forced to suggest going online .

The test report contains the software testers' evaluation of the software quality , So when writing the forecast report, we need to objectively analyze this test activity , Although many enterprises do not require the output of test reports in the project , But Wang Doudou still suggests that each test project should try to output test reports , Don't have to word Documents come and go , Write directly in the email , It doesn't need to be too detailed , Include the main content , Then inform the members of the project team by sending an email .

If there is a partner who needs to test the report template , Reply to the test report in the background .

Finally, thank everyone who reads my article carefully , The following online link is also a very comprehensive one that I spent a few days sorting out , I hope it can also help you in need ！

These materials , For those who want to change careers 【 software test 】 For our friends, it should be the most comprehensive and complete war preparation warehouse , This warehouse also accompanied me through the most difficult journey , I hope it can help you ！ Everything should be done as soon as possible , Especially in the technology industry , We must improve our technical skills . I hope that's helpful ……

If you don't want to grow up alone , Unable to find the information of the system , The problem is not helped , If you insist on giving up after a few days , You can click the small card below to join our group , We can discuss and exchange , There will be various software testing materials and technical exchanges .

Click the small card at the end of the document to receive it

Typing is not easy , If this article is helpful to you , Click a like, collect a hide and pay attention , Give the author an encouragement . It's also convenient for you to find it quickly next time .

Self study recommendation B Stop video ：

Zero basis transition software testing ： Self taught software testing , Got the byte test post offer, Is the B The best video station ！

Advanced automation testing ： Huawei has landed , Salary increase 20K,2022 Most suitable for self-study python Automated test tutorial , Spend it yourself 16800 Bought , Free sharing