tool:
1，JMeter
2，Chrome
4, SwitchyOmega (if required proxy)
step:
These tools will be ready to record after JMeter test script,
Click BlazeMeter plugin in Chrome, the following figure appears:
Can be oriented sub-recording a name, then click on the red origin, began to record a script, then you need to start recording function testing.
Every server request, the numbers will add a plug-in icon BlazeMeter, you can clearly see the steps you recorded.
When the recording is completed, click again BlazeMeter icon, then click the yellow stop button:
Then click on the "jmx" button to export the test script:
Finally .jmx will generate a file, save yourself a name to the appropriate location.
Open Jmeter, file-> open: to find just save the script file, open:
After the open see the following interface description script has been introduced:
Then add a "view result tree" to view details of the test:
If you need a proxy, then also you need to build a "http request default":
Its properties and then fill in the appropriate page of information to the agent (the agent is a global, each request may also set their own agents alone).
Then click on the toolbar of the green Start button:
Switch to "view result tree" view, observe the test results:
The figure we can see the error of the number of requests, information such as the status code returned, the rightmost different labels can switch to a different view of the information returned.
PS: The best test of time the browser is opened only a label, so as not to affect the other pages of the script recording, if the request involves multiple sites, when export script will let you choose:
Select the appropriate site, click to submit.
Transfer from: http: //blog.csdn.net/liushuijinger/article/details/43195973
tool:
1，JMeter
2，Chrome
4, SwitchyOmega (if required proxy)
step:
These tools will be ready to record after JMeter test script,
Click BlazeMeter plugin in Chrome, the following figure appears:
Can be oriented sub-recording a name, then click on the red origin, began to record a script, then you need to start recording function testing.
Every server request, the numbers will add a plug-in icon BlazeMeter, you can clearly see the steps you recorded.
When the recording is completed, click again BlazeMeter icon, then click the yellow stop button:
Then click on the "jmx" button to export the test script:
Finally .jmx will generate a file, save yourself a name to the appropriate location.
Open Jmeter, file-> open: to find just save the script file, open:
After the open see the following interface description script has been introduced:
Then add a "view result tree" to view details of the test:
If you need a proxy, then also you need to build a "http request default":
Its properties and then fill in the appropriate page of information to the agent (the agent is a global, each request may also set their own agents alone).
Then click on the toolbar of the green Start button:
Switch to "view result tree" view, observe the test results:
The figure we can see the error of the number of requests, information such as the status code returned, the rightmost different labels can switch to a different view of the information returned.
PS: The best test of time the browser is opened only a label, so as not to affect the other pages of the script recording, if the request involves multiple sites, when export script will let you choose:
Select the appropriate site, click to submit.
Transfer from: http: //blog.csdn.net/liushuijinger/article/details/43195973