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

Jmeter interface testing practice-create users

I believe that most students who see the title will have questions. Isn't it easy to create a user? call the create user interface, pass in the specified input parameters, and the user can be created successfully. Today, we will talk about creating a scene. There is no problem with creating the user's previous idea through the interface, but it is not that simple in the actual project.

Scene:

In enterprises, most of them have many management systems, such as CMS, CRM, Zhongtai and so on. What they have in common is to distinguish the rights of users, such as: Zhang San is the administrator's authority, Li Si is the department manager's authority, Wang Wu is the general authority.

The main point of this scene is:

The user name is unique.

Different users have different permissions.

According to the general principle of interface testing, it is necessary to repeat three calls to create a user API implementation, and if there are more roles, just repeat it? Obviously this is not the idea we want for interface testing.

There are shortcomings:

The maintenance cost is too high and the script is redundant.

The script is not versatile and has poor scalability.

Some students will want to use csv data config, but csv has limitations. We need to prepare the data in csv in advance, and at the same time, csv files need to follow the jmeter script. If you deploy to different environments, you have to take csv files with you. It's annoying!

Is there any other way? Continue to read on, this article is mainly to expand ideas, to avoid using the previous tweets have been used to play, but also to learn new knowledge points.

Analysis:

Point 1: the user name must be unique and can be done with a random number.

Point 2: create users with different permissions at the same time, then define the corresponding permissions with variables. Permissions in a real project should have a table (in most cases), which can be obtained from DB and then put into custom variables. This demonstration simplifies the steps of reading from DB. Previous tweets have talked about getting array objects from DB and assigning values to variables, so I won't repeat them here.

Do it!

Step 1: new a user sampler in the thread group, and pass in the specified input parameters

UserName is the user name, generated using random numbers

UserJobId is to control user permissions.

The second step is to add random variables under the sampler

It is reasonable to use random variables instead of random functions here. Students might as well try random functions after reading the examples. if you know the answer, you are welcome to talk to me in private, which shows that you have put your efforts into practice. Congratulations on learning this chapter.

Variable name: the user name in json

Output format: because the requirements for creating users are regular, requiring a mixture of numbers and letters and a length between 8 and 30, it is not necessary to configure the random generator, and you will know what the function is by modifying the values several times.

Step 4: add a for Each controller

The output variable JobID is the ${JobId} we used in json to assign values to userJobID.

What about the output variable prefix userjobid? move on.

The fifth step is to add user-defined variables and define user permissions. 1 is an ordinary user and 0 is an administrator. If other permissions are added here, you can also read array objects from DB and assign values to variables.

Now you see, the output variable prefix is here and the value is assigned to the corresponding variable.

Step 6 create a loop controller

Because here userjobid has only 2 values in the custom variable, set the loop once

Finally, let's look at the hierarchical structure.

Add the observation tree and you can execute it.

You can see that two users with different names, CS_zhw36926 and CS_zhw9887, have been created on the result tree. The userjobid is 1 and 0 belong to different roles.

Let's take a look at the response data. Success is returned as ture, and the user has successfully created it.

Data storage check

This is the end of the actual combat explanation.

Through the above methods, an interface test script satisfies the creation of multiple different user names and different roles at one time, enhances the reusability and expansibility of the code, improves the maintenance-free of the code, and avoids the trouble of taking a younger brother with you wherever you go, such as csv.

Today's recommended reading articles are recommended

Why do interface testing?

JMeter database operation

Jmeter Interface Test-regular expression

JMeter returns garbled code in Chinese

Jmeter interface testing-parameterization

JMeter Interface testing-Basics

Test-impression

Add Wechat to the consulting work

scan a QR code

Welcome self-recommendation and recommendation, need Wechat to push resume!

Please poke the QR code below to learn more.

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.