Novice posting, many aspects are just getting started, please forgive me if there are mistakes, welcome criticism and correction
<project name>
Functional Test Report
revision history
| date |
Version |
illustrate |
author |
approver |
Table of contents
1. Introduction 4
1.1 Objective 4
1.2 Intended audience 4
1.3 Background 4
1.4 References 4
1.5 Definition of terms 4
2. Test Objective 4
3. Test method 5
4. Test environment 5
5. Test/Review Task Product 6
6. Test/Review Criteria 6
6.1 Question levels are 6
6.2 Test/Review Pass Criteria 7
7. Test results 7
7.1 Summary of test questions 7
7.1.1 Results of the first round of testing 8
7.1.2 Results of the second round of testing 8
7.2 Other system defects 9
7.3 Analysis of test results 9
8. Test conclusions and proposals 9
8.1 Test conclusion 9
8.2 Proposal 10
9. Appendix 10
1 Introduction
1.1 Goals
This "Functional Test Report" document for <Project Name> helps to achieve the following goals:
Understand the objectives, content, methods, environment and standards of testing/review;
Understand the task product of the test/review;
Give the test/review results and their analysis;
Give the conclusion of the test/review and its improvement proposal to the system
1.2 Intended audience
Project management personnel on the client side, business personnel who join in the research and development of this project
The project functional tester
The project test manager, etc.
1.3 Background
[A brief description of the test object (component, application, system, etc.) and its goals. The information that needs to be included is: the main functions and characteristics, the structure of the test object, and a brief introduction to the project goal. ]
1.4 References
[List the documents referenced by this implementation, for example:
• "XXXX System Requirements Specification", [version], [date]
• "XXXX System Data Dictionary", [version], [date]
• "XXXX System Outline Plan", [version], [date]
• "XXXX System Operation Manual", [version], [date]
]
1.5 Definition of terms
[Conceptual explanation of some technical terms mentioned in the plan]
2. Test objectives
[stop describing the objective of **testing/reviewing]
3. Test method
[Describe **testing/review method, pace, for example:
Use black box testing method to carry out functional testing;
Record defects and errors in a timely manner;
For functions that require data legality and data boundary value checking, add corresponding test cases;
run the test case;
Check whether the test results conform to the business logic;
Combined with robustness test results, review function test results;
After the developer modifies the original code, the test team needs to re-test according to the "Test Case".
]
4. Test environment
[Draw pictures/list descriptions** The test environment that needs to be built for testing/review, the hardware and software in the test environment, including the configuration of test tools. For example:
| equipment |
Hardware Configuration |
operating system |
Database and Helper Software |
quantity |
| server |
PIII866; 512M RAM or more; 10G hard disk space or more |
Windows NT server 4.0 |
SQL server +7.0pack3 SQL server 2000 |
1 set |
| machine |
PIII450; more than 64MB memory; more than 100M hard disk space |
Windows98 |
Office |
1 set |
| PIII450; more than 64MB memory; more than 100M hard disk space |
Windows2000 |
Office2000 |
1 set |
|
| PIII450; more than 64MB memory; more than 100M hard disk space |
Windows NT |
Office 2000 |
1 set |
|
| PIII450; more than 64MB memory; more than 100M hard disk space |
Windows XP |
Office2000 |
1 set |
|
| Network Configuration |
The network should be guaranteed between the client and the server |
|||
| other software |
PowerBuilder8.0 development tool; InstallShield installation tool. |
|||
| printer |
1 set |
|||
One truth per day
Youth is a nectar made of blood drops of will and sweat of hard work—the fragrance will last forever; An impregnable fortress built with persistence and tenacious tenacity—impregnable as gold.
5. Test/review task product
[The list describes the task products that occurred during the testing process, and indicates which ones should be delivered to the customer, for example:
"Functional Test Implementation Plan"
"Functional Test Case" and its case statistics table
"Functional Test Report" and its appendices
]
6. Test/Review Criteria 7. Standards
7.1 Question levels
[Explanation **question-level definitions for testing/reviewing]
1) Fatal problem: It is seriously destructive, 2) makes the system unable to execute or 3) a certain device cannot be used.
These include the following errors:
Illegal exit due to crash caused by the program
Infinite loop
database deadlock
The database schema does not meet the requirements of third normal form or the formatting level of the requirements specification
function error
Error connecting to database
data communication error
4) Serious functional problems: make the system 5) unstable, or corrupt data, or produce erroneous results, and 6) are a major problem that occurs frequently in routine operations or is not 7) avoidable in non-routine operations.
These include the following errors:
program error
program interrupt due to wrong operation
program interface error
Constraints such as database tables, business rules, and default values are not added to completeness
8) Warning problems: system response time slows down, wrong intermediate results occur but not 9) Infinitely affecting the final result, 10) For example: the performance is not 11) correct but the output is correct; general errors, 12) not 13 ) affect system operation.
These include the following errors:
Errors in the operation interface (including whether the definition of the column name in the data window and the meaning are consistent)
Print content, format error
Abbreviated input limit not placed in foreground to stop control
Delete operation did not prompt
There are too many empty fields in the database table
14) Suggested issues: spelling errors in the interface or inappropriate user applications. 15) Minor issues such as convenience or issues that need to be improved; the processing results are correct, 16) the content of the performance is not 17) understandable.
These include the following errors:
The interface is not standardized
The help description is not clear
Irregular input and output
Long operation does not prompt the user
The prompt window text does not use industry terms
Typed and read-only areas are not clearly distinguishable
7.2 Test/Review Passing Criteria 7.3
[Describe** what level of test/review results achieved, that test/review passed, e.g.:
After multiple rounds of system testing, no fatal or functional errors were detected, and special circumstances need to be discussed and decided by the three parties. Warning and proposed questions can be confirmed by XXXX to decide whether to pass or not.
]
8. Test results
8.1 Summary of Test Questions
(Example: Aggregate Reference Chart for Stopping Two Rounds of Testing)
8.1.1 Results of the first round of testing
8.1.1.1 Summary of Test Situation
| serial number |
test date |
application time |
number of people |
Applications |
invention problem |
| 1 |
8.1.1.2 Test question level distribution
Question distribution data table: (unit: number/question)
| fatal |
Function |
alarm |
proposal |
total |
|
| first round of testing |
Problem distribution map: (X-axis: level of problems, Y-axis: number of problems)
(reference picture)
8.1.1.3 Test Question State Distribution
| total number of questions |
Corrected (a) |
Uncorrected (a) |
*Before the start of the second round of testing, XX errors have been corrected, and the rest belong to the understanding of the testers.
8.1.2 Results of the second round of testing
| serial number |
test date |
application time |
number of people |
Applications |
invention problem |
| 2 |
8.1.2.1 Test question level distribution
Question distribution data table: (unit: number/question)
| second round of testing |
fatal |
function/performance |
alarm |
proposal |
total |
|
| retest |
||||||
| Regression Testing |
||||||
| random test |
Problem distribution map: (X-axis: level of problems, Y-axis: number of problems)
(reference picture)
8.1.2.2 Test problem state distribution
| total number of questions |
Corrected (a) |
Uncorrected (a) |
8.2 Other System Defects
8.3 Analysis of test results
9. Test conclusions and proposals
9.1 Test conclusion
[According to the specific project description and the final test results, give a correct evaluation of the system
The following should be included for reference:
1. The final test results found X detectable errors, what kind of errors are they, and whether they have an impact on the application of the system;
2. X non-reproducible errors were found in the final test results, which will affect the system;
3. What is the significant trend in the number of false results in each test phase;
4. The remaining questions pose to the system. . . . Influence. . .
]
9.2 Proposal
(Propose system improvements based on functional test conclusions)
10. Appendix
(Write appendices according to specific projects, such as: )
Appendix 1: Summary of the first round of test questions of "XXXX Processing System"
Appendix 2: Summary of Second Round Retest Questions of "XXXX Processing System"
Appendix III: Summary of Second Round of Regression Test Questions in "XXXX Processing System"
At the end of the article, I would like to share with you some jokes from programmers: There are only 10 types of people in this world: those who understand binary and those who don't.