What is a test report?
Test report refers to the process of testing and the results of written documentation of the findings and defect analysis, provide the basis for remedying the problem of software quality, while laying the foundation for acceptance and delivery of software.
A detailed test report contains sufficient information, including product quality evaluation and testing procedures, test report is based on data collected in the test and the analysis of the final test results.
The structure and content of the test report
The following template examples cited
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
XXXXXXXXX platform test report
2020 March 4
Version History
version | Version Date | Modifier | Remark |
V3.0.2 | 20200102 | Shuangmu month | Create documents |
table of Contents
1 Introduction .... 1
1.1 purpose of writing ... 1
1.2 intended audience ... 1
1.3 References ... 1
Definition 1.4 ... 1
2 test .... 2
2.1 2 test subjects ...
2.2 Test environment ... 2
Test range 2.3 ... 2
2.4 Test Method ... 14
Defects measuring 2.5 ... 14
2.5.1 the number of new Bug day. 14
2.5.2 Bug number of submissions per person. 14
2.5.3 Bug type statistics. 15
2.5.4 Bug severity of the statistics. 15
2.5.5 Bug state statistics. 15
2.5.6 Bug Solution statistics. 15
2.5.7 Bug module number. 16
2.5.8 the number of person to solve the Bug. 16
3 remaining issues .... 16
4 Test Summary 17
1 Introduction
1.1 write Objective
n summary XX XX version of the test platform of work content, process, statistical analysis of test results, whether summary achieve the desired goals, decision-making basis for the release.
1.2 Audience
n products, development, testing Members
1.3 References
Demand analysis of each platform document, the document prototype, test and analysis documents, test documentation, test report document. May be attached to the specific document path.
1.4 Definition
The article describes in some detail to explain jargon.
2 test process
The main course of this test is carried out in detail.
2.1 test object
XX XX version of the new platform or edit content, or interface testing, performance testing, and all involved need to test part.
2.2 Test Environment
Tested under what circumstances, such as a test environment.
2.3 Test Range
XX XX platform version of the test range is as follows:
The main test items | checking point | Test Results | principal |
XX module | XX function is normal | by | Shuangmu month |
2.4 Test Methods
Description of test methods, such as manual testing, automated testing, performance testing tools to wait.
For example: mainly for manual testing. Performing the test analysis and test cases, to ensure that the test coverage range; has to be tested after completion of the original function with the new test cases, the original function of the use cases covered.
2.5 test cases covering
The total number of test cases XX version XX platform is 890, up to the stop 2020 on February 19, use cases were performed 890, a use case not performed 0, execution rate of 100%; wherein the test by the number of use cases 845, accounting for 94.94%, with the number of cases the test fails 32, accounting for 3.6%, blocking 13 the number of cases, accounting for 1.46%.
2.6 Defect Analysis
2.6.1 the number of new Bug day
A defect on the statistical system theme, such as the Zen JIRA like.
Number Bug 2.5.2 submitted per person
A defect on the statistical system theme, such as the Zen JIRA like.
2.5.3 Bug type statistics
A defect on the statistical system theme, such as the Zen JIRA like.
2.5.4 Bug severity of statistics
A defect on the statistical system theme, such as the Zen JIRA like.
2.5.5 Bug state statistics
A defect on the statistical system theme, such as the Zen JIRA like.
2.5.6 Bug Solution Statistics
A defect on the statistical system theme, such as the Zen JIRA like.
The number of modules 2.5.7 Bug
A defect on the statistical system theme, such as the Zen JIRA like.
2.5.8 Bug number per person addressed
A defect on the statistical system theme, such as the Zen JIRA like.
2.7 remaining issues
No. | BUG number | severity | Problem Description | Remark |
1 | 00002 | 1 | Log function failure |
3 test summary
1, XX XX version of the platform as of July 19, 2018, recorded a total of 1837 issues, has closed 1785, resolved not closed 43 activates nine. Activation problem severity of the problem which has 1 to 3, the severity of the problem has three 2, 3 problem severity is 3, 4 severity problems are 0.
2, the new bug situation from the point of view every day, 2020 18 February added 49 bug.
3, from the module bug quantitative point of view, a greater number of functional modules issue: XXXXX, please pay attention to more functional problems, identify problems more multi-functional, may have hidden problems you have.
Recommendation: Fixed issues also need to verify close to finalize remaining issues no serious kind of problem does not affect the normal use of time to finalize the development version.