I practice some of the software performance testing experience sharing



First of all, performance testing is not feasible and impractical for all business.

(1) Choose business with a larger business volume, such as an e-commerce platform tomorrow 10 o'clock in the morning there is a special sale, then this special sales will be a large number of business users, so before going online to do a good job of testing before deciding whether to go online.

(2) need to focus on the business, such as the corresponding e-commerce platform for users to order, submit orders, if in the same period of time the number of orders generated by a platform less, then the company is not tolerated.

(3) The business that consumes the system resources is not a small amount of business.

(4) The most common use of the user, the most frequent operation of the business to do the test (for example, the GIS map Zoom, zoom out, translation is the business focus of testing).

I combined my previous work in the actual test situation, the most prone to problems, listing a few of the following situations:

1, the user login or access the process of the page, contains a large number of computing functions, each user login to do the next calculation (such as real-time statistics of the various districts of Shanghai students Learning data), and the results of the calculation displayed on the page. If it's a single-user scenario that doesn't feel obvious, but in the case of concurrent access with a large number of user accesses, it's foolish and prone to problems.

2, example: E-Commerce Product List Display page, here bread contains commodity calculation sorting function, if the quality is not high code, also prone to performance problems.

3, the e-commerce system to submit the order function, poor quality programming easy to appear database deadlock.

4, similar to the OA workflow system process, if from the previous step, the process to move to the next time, prone to problems. , such as the court case from the previous step to the next, the resulting court case number error.

5, e-commerce backend system, concurrent sales, there is a negative inventory.

6, Large data volume of the query, prone to problems.

7, on-line learning system, in the large number of concurrent learning, learning time overflow, there is a negative study time situation.

Description: Many factors determine software performance, such as hardware problems (hardware configuration), network problems (insufficient network bandwidth), program architecture design issues (a large number of business operations on the same table), connection configuration issues (WebLogic connection pool configuration problems)-- What I've covered in this article is only from the perspective of the program itself.

Soundwill
2016-5-5

I practice some of the software performance testing experience sharing