Recently, I was independently responsible for the performance test of a project and encountered many problems, but when the problems were solved one by one by myself, it was very fulfilling and very fulfilling. Since it is the first time to be independently responsible, there are many places where the preliminary preparations are not thoughtful. It can be said that due to insufficient preliminary preparations, there have been many detours in the implementation of the performance test. Now to summarize.
1. When assigning a project for you to do performance testing, you must have a good understanding of the business process, that is, the function, which must be familiar to you.
2. Secondly, interface documentation and documentation of the interface to be tested are required, because not all interfaces need to be tested. As for which ones should be tested and which ones should not be tested, if there is no clear requirement, be sure to communicate well with development and products, and don’t be blind. If you don't talk about it, you will waste your time and you won't be able to keep up with the progress, and the leaders will be dissatisfied.
3. In addition, there must be documents of database tables, documents corresponding to interfaces and databases (that is, those tables involved in each interface), the business process of database data, and which table the data flows from, which must be clear. It is related to the subsequent data creation. If you do not know the regular flow of the data in the database table, you cannot create the data. The data creation is not a matter of inserting the data into a stored procedure, because if the data is incorrect when the stress test is performed later, it will be reported to each There is no way to measure the error. It is best to use the program to create the database data, that is, to simulate the user to operate and insert data. This kind of data is the most accurate. Of course, you can use LR to set up multiple users to run, because this stored process is difficult to simulate, and you need to know a lot. Rules are not as fast as procedures.
4. For parameterized data, there must be enough data. It does not mean that the query operation only needs to turn off the cache. Indeed, turning off the cache query does not affect the response time. . . . . back home. . to be continued.