Python Performance Test Plan

Hi guy: If you notice the creation time, that's right. This article was written after I learned Python for a month. After writing this plan, we only completed the first step. The process of writing code is a large part of the time completely written in txt. The difficulty is conceivable. After joining a large number of technical discussion groups, I learned a lot about practical and efficient skills and tools. Less than a month after writing this article. Now, there is a good idea for distributed testing, that is, using ssh and ftp protocols in windows. In terms of this idea, it is also difficult to improve it into an automated testing framework. Creation Time: a.m. on Tuesday, July 16, 2013 | classification: python | word count: 647 | sent to my Qzone | save... | print | add to calendar Step 1: Use python for socket protocol sending, link the server with TCP protocol, and process the server response packet.
Thread concurrency, log output, reading excel parameterization, reading DB data, mail Notification of test completion;
The Protocol content is also parameterized, and a certain text format is developed. The protocol specification is used to form a linear logic sequence protocol package.
To achieve the following objectives:

1. Verify the protocol validity and server security, send various broadcast protocols, capital consumption agreements, discount agreements, and gift agreements;
2. Verify the Function effectiveness. The backend, front-end, and server configurations are fine-tuned. Due to high coupling between system modules, functions cannot run normally;
3. Verify the value validity. Read the excel configuration and DB data on the server, and manually import the server back-to-package data into CSV for excel (first, CSV, and then automatically import excel );

The second step is based on the first step. Use protocol packets to send and receive time interval records, protocol sending records (TPS) per second, and use nmon on the server to record memory consumption, CPU usage, and other information.
To achieve the following objectives:

1. Verify the server. In some key scenarios, the server carries the pressure and works with relevant personnel to develop the log record specifications. (Make a csv file first and then import it into an excel file automatically to generate a chart );

Step 3 is based on step 1. Simplehttw.vrice is used as the web Front-end to form a visual testing tool.

1. input the parameter protocol package originally entered in the background to the frontend;
2. Add the configuration modification port, log output, excel parameters, mail format, path, and so on;

Step 4 is based on steps 2 and 3. Use the page chart tool.

1. Add the concurrent Configuration Port, IP address, port, concurrency, concurrency, and scheduled concurrency;
2. Generate a server pressure scenario chart;

Step 5 is based on the previous four steps. A Distributed Stress Testing Tool.

I still don't know how to do it. I didn't know how to do it at the beginning. Now I want to use the open-source framework of IBM. If staf is interested, go to google.