One , The project manager often arranges test engineers to do the following work

* The maximum number of concurrent users of test system
* Test system 8 Maximum business throughput per hour
* Test the stability and robustness of the system
* Test the system when the data reaches 100 Performance with 10000 records
* Test whether the corresponding time of the core transaction of the system meets the needs of users
Two , Performance testing concept

* It is to test whether the performance of the system meets the requirements of production performance by simulating the business pressure of production operation or user usage scenarios .
* Performance testing is a “ normal ” test , It mainly tests whether the system meets the requirements during use , At the same time, it is possible to make a little more than that in order to reserve the expansion space of the system “ normal ” Range
Test of ( such as : Current system users 100 people , It is possible that the number will increase to 300 people , So the system should be able to 300 Normal operation under human condition )
Three , Load test

* By gradually increasing the system load , Test system performance changes , And under the condition of meeting the final performance index , Test of the maximum load that the system can bear
performance index : The system should be satisfied , Such as request response time, etc
Load tests are normal range tests
Four , Stress testing

* Gradually increase the system load , Test system performance changes , Finally, the system performance is in failure state under what load , And in order to obtain the maximum service level that the system can provide
Five , The difference between stress testing and load testing
Similarities : It's all performance testing
Load test emphasizes the performance index of the system under normal working condition
The purpose of stress testing is to find out under what conditions the performance of the system becomes unacceptable , Find inflection points for application performance degradation .

give an example : Workers build bridges , The bridge shows , The maximum weight of the bridge is 60 ton .— Load test
In the internal building information of the bridge , It shows that the maximum load capacity of the bridge is 70 ton . This data is for internal bridge engineers to master .— Stress testing

Six , Main factors affecting system performance

* Hardware :CPU, Memory , Hard disk , Network card and other network equipment
* operating system
* network
* middleware ( Also called application server , as Jboss,websphere,weblogic etc. )
* Data server
* client
* programing language , Program implementation mode , algorithm
Seven , Common terms for performance testing
1, Concurrent : Multiple users at the same time , To perform an operation together ; The requirements of concurrent testing are strict , Focus on the instantaneous pressure of the system
on-line : Multiple users operate on the system over a period of time ( It refers to a multi-user online loop operation of an action )
For general systems , Multiuser concurrency and multiuser online pairing AUT The pressure is 10:1, Namely 50 User concurrency is equivalent to 500 User online
2, Request response time

* It refers to the timing of sending a request from the client , The timing ends when the client receives the response result returned from the server .
* In some tools , Request response leave is often referred to as TTLB(Time to last byte: Start by sending the first request , The time taken until the client receives the last byte response )
* The unit of request response time is generally “ second ” or “ millisecond ”

* Request response time = Client time + Network time ( Transmission time )+ Server time

During the actual project testing process , The system under test is often deployed to the Intranet environment , There is plenty of bandwidth , The bottleneck of network can be avoided .( Because the network is uncontrollable , It's provided by the operator , Uncontrollable , Notice that it's the system , Not the Internet , If system test , Finally, it is a network problem , It can't be solved .)
* Performance testing concerns two words : Request and response . The normal order is request and reply , Send first and receive later
3, Transaction response time
The user completes a specific transaction ( Such as inter-bank withdrawal ) Time required
On performance testing

* During the performance test , The database cannot be empty or has few entries , In this case, the test does not conform to the actual production situation . It must be based on the actual online situation of the system , Insert enough data ( Background data ) Then test
* Before performance testing , To test the system (AUT,application under test) Make a backup ( Database backup )