The complete process of performance testing work, the purpose, and what is most critical

The complete process of performance testing work, the purpose, and what is most critical

System Test Categories: Functional testing (correctness, fault tolerance, concurrency logic, associated content), security testing, performance testing (stress testing, response time), strength testing, capacity testing, recovery testing, user interface testing, inter-interface testing ...

The concept of performance testing---to test the performance of the system under normal, peak and abnormal load conditions, and to simulate it through automated test tools.

Performance testing is mainly to test whether the various indicators in the operation of the software meet the requirements; Stress testing is the focus of performance testing, which is to simulate the actual running state of a software system by means of tools to generate and run concurrent transactions to obtain various performance indicators.

The purpose of the performance test---

1) Assess the capabilities of the system----the load and response time data obtained during testing can be used to validate the planned model and help make decisions.

2) identify weaknesses in the system----the controlled load is increased to an extreme level, and break through it, thus repairing the bottleneck or weak place of the system.

3) System Tuning---Repeat the test, verifying that the activity of the tuning system has the desired result, improving performance. Detect problems in software, long-time test execution can cause a program to fail due to a memory leak, revealing hidden issues or conflicts in the program.

4) Verification of stability, reliability---testing at a given time is the only way to assess the stability and reliability of the system to meet the requirements.

The content of the performance test---

Load test, pressure test, capacity test, network performance test

Among them, the capacity test, load test, strength test in English explained as:

Volume testing = Large amounts of data

Load testing = Large amount of users

Stress testing = Too Many users, Too much data, Too little time and Too little

Performance test (performance Test): Generally collects all the performance related to the test and is usually used by different people in different situations.

Focus: How much and how fast

Load test: A load test is a performance test that refers to whether the data is running in an overloaded environment and if the program can afford it.

Focus: How much

Strength test (Stress test): Strength test is a performance test, he in the system resource is particularly low in the case of software system operation, the purpose is to find out where the system fails and how to fail the place. Including

Spike testing: Extreme load test for short periods of time

Extreme testing: Load test under excessive user

Hammer testing: Perform all the actions you can do continuously

The purpose of the stress test:

1) Identify bottlenecks that affect system performance

2) Evaluate system performance

3) Optimization of system resources

4) Increased response time and throughput

Another task when running stress tests is to monitor system resources and use tools to monitor and document resource usage.

The monitored objects are: network congestion, host CPU usage, memory usage, cache usage, data locks in database systems, rollback segments, redo log buffers, and so on.

The results of the monitoring include images and data files, and the images can be displayed in real time, and can be analyzed after the stress test run is over. You can use the monitoring tools that are included with the operating system and database system software.

Through the results of resource monitoring, it is easy to find the bottleneck of the system and adjust and optimize the resources that produce the bottleneck.

It may be confusing to see performance tests, load tests, and strength tests. Yes, these three concepts are relatively easy to make people confused. Load and strength tests are subsets of performance tests. Here's a running example to explain.

A performance test that represents the best situation to perform under a given benchmark. For example, how long does it take you to run 100 meters without a load (this way, no weight is the benchmark)?

The load test is also a performance test, but he is under a different load. For just that example, if the extension is: in 50 kg, 100 kg ... How long will it take you to run 100 meters in such a situation?

Strength testing is a performance test in the case of strength. For that example, if you change to a strong wind, how long does it take you to run 100 meters without bearing or bearing?

The complete process of performance testing work, the purpose, and what is most critical