Shulou(Shulou.com)06/02 Report--

Tutorial 2 mentions building scripts through templates, and the principle of recording is to set up a proxy server, so let's switch to Recorder, as shown in the following figure

There are three red boxes in the picture, all of which are more important.

The first red box indicates the address of the local proxy server. Once you need to record, you need to set the Internet settings-connection-proxy settings.

The second red box is grouping, and the default is to automatically establish transaction transactions on request, similar to LR's. But my experience is to choose not to group, and then manually set up transactions, so my option is "do not group samples."

The third red box area is filter, which is generally used by default. The default exclusion mode will remove all static resources, because the static resources of general websites are all CDN, so there is no need to stress testing, this configuration is to support regular. Of course, the default value given before 2.12 is a little flawed, and since we use 2.13, we don't have to care too much about this configuration.

Click enable directly after the configuration is completed, and the proxy server will start to work.

If the Internet connection agent in the screenshot above takes effect, any http requests you send during the browser operation will be recorded exactly to the Recording Controller in TestPlan.

At this point, we can record the script without any scruples.

But for beginners, this is not the end. I would like to share some of my work experience:

Transactions in LR are often made up of one or more requests, and the same is true in jmeter, so when you feel that you have completed one of your transaction operations. You can shift check multiple requests to right insert the superior-logic controller-transaction controller. This facilitates the logical layering of many requests.

There are usually a lot of miscellaneous requests in the recorded scenes. For example, when I record Google search, there are usually a lot of management requests in addition to search. Usually, we just test the business itself, not test management, and so on. So we can disable some unnecessary requests according to domain (right click)

For some commonly used values, for example, for example, my test beta environment domain is w.51ping.com, and online w.alpha.cn, then I can variable some parameters and put them in the User Defined Variables of TestPlan before I start recording. When the recording is completed, all values matching will be replaced with the variable writing ${variable_name}.

Basically, if you master the above three tips, the script you recorded will be more perfect, but students who have used LR know that recording is definitely not enough, and often we still need to associate it, so in the next article, we will explain the association of HTTP requests in more detail.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.