Performance Testing
Performance testing refers to the performance indicators of whether the system behavior meets the required specifications under certain conditions. For example, by testing performance indicators such as the longest transmission time limit, transmission error rate, calculation accuracy, response time limit, and recovery time limit, it is verified whether the software system can meet the performance indicators proposed in the requirements specification, and found that the software system The performance bottleneck existing in the system achieves the purpose of optimizing the software system.
performance test index
-
concurrent number
- Number of system users: the number of registered users of the system. For example, QQ has 100 registered users.
- Number of online users: the number of logged-in users. For example, 60 out of 100 people are online.
- Concurrent users: It is the users who put pressure on the server. For example, only 20 of these 60 people are communicating or otherwise operating. These 20 people are the number of concurrent users.
-
Response time (request response time) Request response time is usually referred to as "TTLB" (Time to last byte), which means the time it takes from the time a request is initiated until the client receives the last byte of response. The time required to respond to a request is generally: network request time + server processing time + network response time
-
Transactions per second (TPS) refers to the number of transactions that the system can handle per second. It is an important indicator to measure the processing power of the system.
-
Throughput is the number of client requests processed by the system per unit time. It directly reflects the performance carrying capacity of the software system, and is generally measured by the number of requests or pages. From a business point of view, throughput can also be measured by the number of visitors/day or the number of transactions processed/hour; from a network point of view, throughput can be measured by bytes/day.
-
Resource Utilization The usage of different system resources. CPU, network, disk, network.
Classification of Performance Tests
Performance testing is divided into narrow performance testing, benchmark testing, strength testing, security testing, recovery testing, installation testing, reliability testing, configuration testing, usability testing, compatibility testing and documentation testing.
| test | introduce |
|---|---|
| narrow performance test | Performance testing in a narrow sense tests whether the performance of the system can meet the requirements of the production system by simulating the combination of business pressure and usage scenarios in production operation. is a common test method. |
| Benchmarks | Benchmark test refers to the quantitative and comparable test of a certain performance index of a class of test objects by designing scientific test methods, test tools and test systems. |
| Strength Test (Load Test) | Increase the stress on the system under test until performance is extreme. Test the changes of various performance indicators of the system when the load gradually increases; find the load limit of the system to provide data for system tuning; check the operation of the system under overload conditions. |
| security test | Test the system's ability to prevent illegal intrusion |
| recovery test | Test the fault tolerance of the system. Various manual intervention methods can be adopted, such as deliberately injecting some software faults into the operating system, creating interference on the communication line, citing invalid pointers in the database, etc., so that the software fails to work normally due to errors, and then the recovery ability of the system is tested. |
| installation test | Find out what went wrong during those installs, not software glitches. |
| reliability test | Test whether the mean time between failures exceeds the specified time limit and the time of downtime due to failure |
| configuration test | Configuration testing is the process of checking software operation with various hardware and software platforms and different settings to ensure that the tested software can use as diverse a combination of hardware as possible. |
| usability testing | Usability testing checks whether users are satisfied with the software. |
| compatibility test | Test whether the software is forward and backward compatible, and whether it is compatible with different versions |
| Documentation Test | Detection documentation |
Performance test steps
- Develop goals and analyze systems
- Choose a method for testing metrics
- Adopt related technologies and tools
- Develop evaluation criteria
- design test cases
- run test case
- Analyzing test results
If the article is helpful to you, remember to like, bookmark, and add attention. I will share some dry goods from time to time...
END Supporting Learning Resources Sharing
Finally: In order to give back to the die-hard fans, I have compiled a complete software testing video learning tutorial for you. If you need it, you can get it for free 【保证100%免费】
Software Testing Interview Documentation
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.
How to obtain the full set of information:
