Performance test report (scenario) template

1th Chapter Overview 1.1 Purpose explain why this test is performed, what the participants are, when the test time is, and the project background. The purpose of writing this test scenario is to determine whether the software meets the performance requirements of the product, and to identify the performance bottlenecks in the system and to optimize the system. Testing is based on the requirements of the product specification; If the user does not propose performance indicators, according to user needs, test designers experience to design the test indicators. This template enables scenario design and test report records for performance testing. 1.2 name-word explanations The professional terminology of the business and technical aspects involved in this scenario. 1.3 reference materials all documents referenced and based on this scenario. 2nd Chapter Test Demand Analysis 2.1 Test Purposes describes the purpose of this test. For example: 1, IAGW added SMS filtering function and authentication function, need to perform performance test, get the performance index of the system, 2, carry on the big pressure test continuously, carry on the stability test to the system. 2.2 Test Objects describe the name, version, and feature description of the product being tested. For example: Product NAME:IAGW License version:v1.1 build date:20060715 2.3 System Structure briefly describes the structure of the system under test. 2.4 Test Range 2.4.1 Test Range such as: XXXX system performance indicators, software response time performance testing, CPU, Memory performance testing, load performance testing (stress testing) 2.4.2 Main test content such as: 1. Response time for typical applications 2. Client, server CPU, Memory usage 3. Server response Speed 4. The optimal number of loads supported by the System 5. Network index 6. System Reliability test 2.5 System Environment describe the hardware and software environment required for testing. 2.5.1 Hardware Environment

IP	CPU	OS	Memory	Storage
10.3.3.96	3.00GHz *2	Suse9	2G	135G

2.5.2 Software Environment 2.5.2.1 test software products mainly describe the SOFTWARE Product module name and the distribution of each module.   The 2.5.2.2 Test tool describes the test tools used. The 3rd Chapter test Scene Design 3.1 Scene 1 describes the business operations at the time of test execution. is equivalent to use case. Under different scenarios, different test results will be obtained. Therefore, the results of the performance test must be associated with the scenario. For example: Test IAGW The maximum number of SMS messages processed per second, under the restriction of multiuser concurrent access transaction response time <3 seconds, without communicating with other servers. 3.1.1 Test Purpose describes the purpose of this scenario test. For example: IAGW handles the maximum number of message bars per second. 3.1.2 Test Configuration describes the configuration used by this test 3.1.3 Test Steps describe the test steps in detail. For example: 1, the use of mobile phone simulation tool at the same time to send the IAGW 10,000 Shenzhou Mo and Global pass Mo 2, using Testtool received all MO SMS 3, Record server Resource Usage 4, all the message processing finished records processing results 3.1.4 Test Results Output Record the test output, and reflect the results of the test data table, chart truthfully to the test results. for data analysis. For example:

Number of SMS (million)	Time (SEC)	Average Speed (Bar/sec)	Maximum speed (Bar/sec)	Minimum speed (Bar/sec)	IDLE occupancy rate (average,%)	MEM usage (average,%))	CPU usage (average,%)

Note: This section is not included in the performance test scenario and is only available in the Performance test report. 3.1.5 Test Conclusion The records the test output results. for data analysis. For example: In the case of handling 10,000 Shenzhou lines and global MO messages, SMS processing speed is 400/sec. Test results contrast: IAGW1.1 SMS Maximum processing capacity of 330 Bar/sec, the release of the IAGW1.1 performance slightly improved. The modules run stably.   Note: This section is not included in the performance test scenario and is only available in the Performance test report. &NBSP;