Things to note about performance testing

I have done performance tests several times before, and I would like to share with you a little bit of my experience.

From the beginning of the test requirements to the completion of the test, we need to go through many stages

. The first is the test requirements. To evaluate whether the test requirements are reasonable, not all performance test requirements are required. All need to arrange the test directly, but to evaluate whether this performance test needs to be done.

It is based on the user's consideration that the product requires performance testing. If it is determined to perform performance testing, it is necessary to evaluate the performance testing scheme. Including the time of environment construction, logical understanding, data preparation, testing process, problem location, modification and optimization, regression, and reporting. It should be emphasized that the time when the performance test starts must be when the functional test has passed. Otherwise, the performance test will modify the function logic and cause the performance to change, and the performance test will have no guiding significance.

The construction of the test server and the construction of the suppression environment. The test environment can be built by development. In principle, the configuration of the test server cannot be higher than that of the online server, and the services deployed on the test server should be as close to the online server as possible.

Understand the business logic of the entire performance test. Generally, you need to know the number of requests, the meaning of request parameters, etc. In addition, here are a few issues that are easily overlooked by newbies: that is, when suppressing the test server, it must be clearly isolated from the online server. Don't simply think that all requests are directed to the test server, that it is only suppressing the test server.

The difficulty of performance testing lies in the understanding of the system under test and the analysis of the test points. In order to realize the idea of ​​​​testing, there can be many methods, the means are always only auxiliary, only the idea is fundamental. Tools are not equal to performance testing. Don't think that you can understand performance testing by using LR. It is only the lowest level of test execution. Don't think that you can understand the performance test by adjusting a few parameters, it is also a relatively low level.

Tuning and other techniques are not the main purpose of performance testing, and good performance is not tuned out. Testers must understand the value of their existence. The so-called "technology" is only some means to achieve their own testing purposes.

How to prove the validity of the test results is actually a difficult problem, and it is worth spending time to think carefully. This process involves some very important content, such as the establishment of a user model, which will be detailed later.

Performance testing is a process that requires continuous improvement. Just try to do better every time, and do a little more things that were not thought of before. After continuous accumulation, you will find yourself with a deeper understanding of performance testing.

Performance testing is an important test item for products, and it is a guarantee to ensure product quality and user experience. Especially in recent years, with the explosion of mobile products, more investment is required in app performance testing, app cloud testing, etc. These helped.

TestBird