The test report is to document the test process and results, analyze the problems and defects found, provide the basis for correcting the existing quality problems of software, andSoftware acceptanceAnd delivery.
The test report is the final document output of the test phase.A good test manager or tester should have goodDocumentationCapability;
A detailed test report contains sufficient information, includingproduct qualityAnd the evaluation of the test process. The test report is based on thedata acquisitionAnd the analysis of the final test results.
content
Announce
edit
Content of test report
The contents of the test report can be summarized as follows:
The specific purpose of this test report is to indicate the intended audience.
Example: This test report is the test report of XXX project, which aims to summarizeTest phaseTesting andAnalysis testAs a result, describe whether the system meets the requirements (or reaches XXX functional objectives).Expected reference personnel include users, testers, developers, project managers, other quality management personnel and senior managers who need to read this report.
listDesign bookSpecial terms and abbreviations of the system/project.For technical related terms andPolysemyBe sure to indicate clearly so that there is no ambiguity when reading.
2.5 References
1. Demand, designtest case, manuals and othersProject DocumentsThey are all within the scope of reference.
An overview of the test, including some statements of the test, the scope of the test, the purpose of the test, etc., is mainly an introduction to the test.(OthersTest ManagerAnd quality personnel)
Briefly introduce the methods (and tools) used in the test.
Tips: mainlyBlack box test, the test method can be written with the test focus and adoptedTest modeIn this way, you can clearly know whether important test points and key blocks have been missed.The tool is optional when usedtest toolsAnd related tools.Note whether it is a manufacturer or a manufacturer, and what the version number is. After the test report is released, avoidcopyrightQuestion.
brief introductiontest caseDesign method.For example:Equivalence class division, boundary value, causality diagram, and using such methods (3-4 sentences).
Tip: If you can specify the design, it will be easy for other developers and test managers to read yourUse CaseThere is an overall concept of design. By the way, it is also beneficial to write some unconventional design methods here. At least you can understand the design technology of the test manager before you see the test conclusion. The key test part must ensure that there are more than two different use case design methods.
This is the most exciting part of the whole test report, which mainly summarizes various data and measures, includingTest processMeasurement and capability assessment ofsoftware product OfQuality measuresAnd product evaluation.For projects that do not need process measurement or are relatively small, such as test reports submitted to users during acceptance and test reports of small projects, the measurement part of the process can be omitted;CMM/ISO or other engineeringStandard processOf, need to provideProcess improvementRecommended and referenced test report - mainly used by the companyInternal testImprovement andDefect preventionMechanism - then process metrics need to be listed.
4.1 Test execution and record
Describe the test resource consumption and record the actual data.(Test and project manager focus part)
4.1.1 Test organization
A simple test group architecture diagram can be listed, including:
Test group architecture (such as grouping, user participation, etc.)
Test Manager (Leader)
Key testers
Testers
4.1.2 Test time
List the test span and workload. It is better to distinguish between test documents and activity time.The data can be used in excessive quantities.
For large systems/projects, the total investment of resources should be counted, and the cost column should be added when necessary, so that managers can clearly know how much manpower is spent to complete the test.
Test Type Personnel Cost Tools and Equipmentother expenses
total
When summarizing the data, you can count the average investment time, total time and overall investment of individualsaverage timeAnd the total time, you can also calculate eachFunction pointHours/person spent.
Total of time consuming personnel writing use cases and executing tests
total
The data used for process measurement in this section includes documentsproductivityAnd test execution rate.
Productivity Personnel Use Case/Writing Time Use Case/Average Execution Time
total
4.1.3 Test version
Give the tested version, if yesfinal report , you may want to report the number of testsregression testingHow many times?The list of tables is convenient to know the test frequency of that subsystem/sub module. The developers will pay attention to the subsystems/sub modules that have been regressed for many times.
4.2 Coverage analysis
4.2.1 Demand coverage
demandCoverageIt refers to the ratio of the tested requirements/functions to all requirements/functions in the requirements specification, and generally it is required to achieve the goal of 100%.
Remarks on whether the requirement/function (or number) test type passes
[Y][P][N][N/A]
According to the test results, give the passing or not conclusion of each test requirement by number.P meansPartially passed, N/A means not testable or the case is not applicable.actually,Requirements Tracking MatrixListsOne-to-one correspondenceTo avoid omission, this table is used to convey test information of requirements for inspection and review.
Demand coverage calculation Y item/total demand × 100%
Requirement/function (or number) Number of use cases Total number of cases Not implemented No/missed test analysis and reasons
actually,test caseIt has been recordedExpected resultsData, the test defect indicates the deviation between the measured result data and the expected result data;Therefore, it is unnecessary to include more detailed description of defect records and deviations here for each number. The purpose of the list is to better view the test results.
Test coverageCalculated number of executions/total number of cases × 100%
4.3 Defect statistics and analysis
Defect statistics mainly involveSystem under testTherefore, this part has become the focus of developers and quality personnel.
user interfaceConsistency function algorithm interface document user interface others
Distribution by function
Function One Function Two Function Three Function Four Function Five Function Six Function Seven
It is better to give defectivePie chartandHistogramFor visual viewing.As the saying goes, a picture is worth a thousand words. Icons can enable readers to get information quickly. In particular, managers at all levels have no time to read articles item by item.
legend
4.3.2 Defect analysis
This part deals with the above defects and otherscollecting data Conduct comprehensive analysis
Comprehensive analysis of defects
Defect discovery efficiency=total number of defects/test execution time
It can be obtained from specific personnelaverage index
Case quality=total number of defects/test caseTotal number × 100%
Defect density=total number of defects/total number of function points
The defect density can get the distribution of defects in various functions or requirements of the system. On the basis of this analysis, developers can get the most defects in those functions/requirements, so that in future development attention should be paid to avoid and attention should be paid to during implementation. Test experience shows that the more defects are tested, the more hidden defects are.
Test curve
Describe the tested system every working day/weekNumber of defectsSituation, get the defect trend and trend
5. Whether it is possible to enter the next phase of project objectives
[1]
5.2 Suggestions
1. Description of the system problems, and description of the problems exposed by the testSoftware defectsAnd deficiencies, as well as possible impact on software implementation and operation
XXX (product or software)/XXX (module) test report
1. Overview
Test purpose Briefly describe the purpose of this test, such as: verify whether a module meets the design
Project background Brief description of the background of the project where the test is conducted, such as: what stage has it entered, andOther information
