I. Introduction
Zhou had a scheduling interface performance tests on the task, began the first interface performance test career. . .
Before interface pressure measurements, we first need to transfer through the script. There are two ways, one is crawling through the service interface packet capture tool (such as fiddler); the other is to record a script by jmeter.
Both are a variety of advantages and disadvantages:
(1) Fiddler manual capture: [advantage] directly grab business interface; [shortcomings] For performance testing of white may be more difficult (such as the author's own, difficult to find a relationship between the business interface);
(2) Jmeter recording a script: [] advantages of the business relationship between the interface may be embodied from a script; [] needs disadvantages (as circled portion of the interface has been disabled) filtering irrelevant their interfaces;
Performance testing because I still white, so we chose to conduct script jmeter recorded in this way.
Second, script recording
According to performance testing requirements, the need to measure the business systems analysis about the number of transactions. As shown above, the analysis results of business information system self-test, fill out the information, fill out a form, upload the material, submit five pieces do business. Add HTTP Request Defaults, look at the result tree, polymerization report, then add a thread group in the test plan.
(1) Right-test plan to add a thread group
(2) new thread group Right Transaction Controller
After adding the transaction controller, while recording a script, you can select the corresponding transaction in the "Target Controller".
Generate parent sample: whether to generate a parent sample, at the request of the forthcoming transaction controller as a whole (usually this option is checked). Check to see the results in the tree and a polymerization reports, only the name of the transaction, the transaction is not specifically request the display.
(3) Add the table right HTTP proxy server (proxy settings correspond to the browser) to select the corresponding target controller, and start recording.
After starting the recording, you can go to business systems related operations, will be recorded at this time jmeter relevant script, the script generated will be displayed in the corresponding transaction, under many interfaces as shown in "self-test information" is generated record. After the transaction operation, remember back to the proxy page jmeter stop recording, when the end of the script recording things.
PS: the image above, the transaction "basic information", "fill out the form ',' upload material", "complete" the recording steps above, but more is described here.
[To be continued ....]