Pressure test flow

First, the pressure measurement process

Refer to the previous pressure measurement countermeasure flow.

Second, the pressure measurement requirements

It is necessary to define the environment for pressure measurement.

Interface to be stress tested, including the parameters of the interface.

The expected qps of the interface needs to be clear.

Online machine configuration needs to be defined.

Third, the pressure test preparation

3. 1, preparation for server development:

1. According to the interface to be tested, decide which related dependent services need to be deployed.

2. Test the service and interface corresponding to the interface.

3. Related configuration

4. Relevant databases

5. The required machine layout, including machine configuration, requires several machines.

3.2, front-end development preparation:

1. Test interface and service application

2. Domain name

3. Machines that need to be prepared

4. According to the interface to be tested, decide which related dependencies to deploy.

3.3, test preparation:

1. Prepare the test plan and test scheme for stress testing.

2. Confirm the stress test scenarios through the interfaces, including the scenarios that each interface needs to test and the expected stress test threads of the interfaces. Confirm the test scheme through the test scenario.

3. Prepare the test script according to the test plan.

4. Prepare corresponding test scenarios according to the situation of each interface.

5. Prepare the required test data according to the test scenario. It will include the login account, data returned by the interface and so on. It is suggested that the online database can be directly copied to the pressure measurement environment.

6. Apply for testing authority of pressure machinery.

7. Prepare tools that need to run on the printing press.

Four, pressure measurement scheme and plan

4. 1. Prepare the pressure measurement scheme and plan.

1. Template view of pressure test plan and plan

2. Integrate the information in the test plan, including the interfaces to be tested and the corresponding time nodes of each process.

3. After the test plan and test scheme are determined, they need to be reviewed with the corresponding personnel (including server development, front-end development, testers, front-end operation and maintenance, server operation and maintenance, etc.). ) to confirm the time node of the final process.

4. Output the corresponding results according to the time in the test plan. Including service vouchers and front-end code deployment, machine application and deployment, and test script output for testing.

4.2, test writing test script

1. Confirm whether the test interface depends on login and whether login information is required.

2. Confirm whether the interface to be tested belongs to atop interface or http interface.

3. Determine which scripts need to be written.

4. Debug the test script 5.

Automation script or jmeter script, you can view the usage of jmeter.

4.3, test verification test script

1. Verify the test script in the daily environment to ensure that the script can run normally.

2. Arrange the preparation data required for testing the interface.

3. Prepare the assertions needed to test the interface.

4.4. Verification of pressure measurement environment of press.

1. Replace the corresponding domain name and data in the test script with data from the stress test environment.

2. Verify the environment and scripts in the stress test environment.

3. Develop and debug problems in the stress test environment and debug scripts.

4.5. Simulate pressure measurement in the pressure measurement environment.

1. Use the interface to simulate pressure measurement, and confirm whether the icon information to be collected and the results are in line with expectations.

2. Confirm whether the press and pressure measuring instrument are normal and whether they need to be replaced.

3. Confirm the collection of data to be collected.

4. Confirm whether the assertion method is ok.

Verb (abbreviation for verb) pressure measurement begins.

5. 1, formal pressure measurement:

1. Start the formal pressure test, and close the pressure test for everyone (development, operation and maintenance, DBA, etc.). ).

2. Determine the order of interface pressure measurement according to the measured values of interface pressure.

3. It is necessary to gradually increase the number of threads in pressure measurement.

4. Observe the correlation between real-time qps and error report in the process of pressure measurement, and inform the developer of the corresponding interface response time for query.

5. According to the interface link, notify the corresponding personnel to check the receiving time and response time during the pressure test.

5.2, pressure test results analysis:

1. After the secondary interface pressure test is completed, analyze the results and confirm qps, error rate, 10%, 50% and 90% user response time after the pressure test.

2. Develop and find the corresponding waste of time. After field optimization, the interface can be stress tested to find the performance bottleneck.

3. The final result of pressure measurement is to find the maximum qps and the number of concurrent errors that begin to appear.

4. If the number of threads corresponding to the current number of threads does not meet the corresponding qps requirements, you can decide how many threads to add according to qps. If the number of threads increases, qps does not improve, and the limit of qps has been found.

5.3, stability test:

1. Find the number of threads corresponding to a relatively stable qps, and test the stability.

2. The difference between stability test and pressure test lies in the duration.

3. Stability testing can be used to observe the performance of the system when interfaces are called continuously.

4. According to qps of stability test and stress test, the corresponding daily activity can be calculated.

Six, after finishing the stress test report

1. test report arrangement

A. sort out the test report of this stress test.

B the test report shall record the time node corresponding to the pressure measurement, the qps corresponding to this pressure measurement and the error rate of this pressure measurement.

C. The response time of 10%, 50% and 90% users was measured this time.

D. Burr time node in the process of pressure measurement.

E. Causes of abnormal curve correspondence in pressure measurement.

F The report needs to be developed and tested at the same time.

G. test records, pressure data and icons

H. Develop and record information such as cpu utilization rate, load and database load of the corresponding system.

A, test report template