How to compile an effective test report

1. Be clearTestReportOfOperating SystemEnvironment:
For example, what is the operating system of XX software? YesWindows98, Windows2000, WindowsXP, orLinuxOperating System. In many cases, most software only has defects on a systemOthersThe version may not have any defects.

2. the test report results are only responsible for the released version and the svn number of the configuration Library:
It may be embarrassing for colleagues. Many tests foundBugAnd record the bug to the bug tracking system. The result is that the bug does not exist on your machine. The tester is required to verify whether the bug exists again. One possibility is that the developer has modified the defect after discovering that the tester has submitted the defect. Another case is that the version release is not standardized and the developer forgot to submit the defect.CodeGo to the configuration Library and the results will be published. Therefore, the test report is only responsible for specific versions and environments.

3. Point out the testedBrowser:
In particular, similar web software and different browsers have different problems. The same browser, different versions, and test results reports are sometimes different. Our department has previously encountered the same function as ie6.0 and ie7.0, and the page display is not the same. Therefore, it is best to describe the problematic browser in the test report of similar web software.

4. test conclusion and TestSuggestionsForValidThe test report is critical:
Test conclusions and test suggestions must be brief and accurate, and sometimes decide whether the version can be released, especially the testing owner. Be careful when reporting the tested software.

5. Test Case execution:
ForSoftware TestingReport types, such:Unit Test, Integration testing,Function Testing,Performance TestingAnd stress testing respectively. Number of executed or unexecuted use cases when preparing the report. Percentage of failed test cases passed. The reason for failure must be described. The test cases of test blocking must be described. It is best to use bold characters to make it clear at a glance.

6. Generally, a list of defects (buglist) must be attached ):
In a software test version, how many problems have been found in the test? What are the severity levels and priority of defects? What are the bugs that have been closed and fixed? What problems are left over from this version? What are the problems solved by the next version? What are repeated defects? With buglist, you can see it at a glance, which is simple and clear.

7. Graphic and data analysis of test results:
To submit a test report, you must differentiate the submitted objects. Different types of persons must submit test reports of different versions. If it is submitted to the R & D department, it is best to attach explanations on defects isolation and other related aspects to help developers quickly locate defects and solve problems. If you submit an object to a customer, you can describe in detail whether the customer's functions and common modules have been implemented and whether there are problems. If you submit your documents to company leaders and customer leaders, they don't have much time to read your text. It's best to look at the test charts.Defect managementTools, such as testderector and qacenter, automatically generate different charts and attach the defects of each function module !!

8. the test report can also include the relevant analysis of the defect measurement:
Such as defect density, etc. Increase the technical content of the defect report.