Jmeter parameterized, the checkpoint set point tutorial

When using Jemeter do stress tests, often requires a parameterized user name and password in order to achieve the purpose of multi-user login using a different user name and password, and this time we can use parameterized login.

A, badboy need to record a script, you can also perform packet capture or jmeter own record (more chaos, more requests) with fiddler

Second, entered jmeter parameterized;

1. Record of the script badboy, import jmeter, add trees to see the results, polymerization report;

2. Perform a thread, into the trees to see the results, see the response data (Recommendation: Review the next HTML), delete unwanted requests in the plan;

 

3. The front of the preparatory work, now entering the parameterized;

Introduces two parametric parts:

(1) If the value range of the parameter is small, the use of the User the Parameters (user parameters).

(2) If a large ranges of parameters, it is recommended to use CSV Data Set Config method, this method has greater flexibility.

 

 

 4. The first parameter to disable use csv out user parameters, find the page username, password.

 

 5. Use Notepad ++ to write, if not it can be (must be written in English mode) with a text document;

6. Set the parameters of the user's password;

 

7. Run it, (remember there are several sets of parameters, to let users meet the number of parameters) used to view the results tree, view the request parameters of the page.

 

 

 (The second parameter is the original error, not a reference, but what we are parameters that have been read and execute)

8. User parameter is relatively simple to add variables plus the horizontal, the user is listed (for small quantities parametric); setting completion can be run directly.

 

Third, the checkpoint: As the name suggests, is to check us into the right to check the content is not the same

1. Add assertion response (asserted), assertion result (listener);

 

2. Locate the response data to be checked (see example landing was successful)

 

3. Configuration Response assert: in response to text -> comprising -> Success; can be understood, and then run it.

 

4. Check the content right is so slightly.

 

5. Check errors.

 

 

 

Checkpoint is very simple (I write is a basic foundation of)

 

Fourth, the rendezvous: Concurrent rely on rendezvous

1. Add Synchronizing Timer (timer)

 

 

 2. Synchronizing Timer drag to set the timing for the upper (e.g.: concurrent landing, landing on top of it, which is not)

 

 

 3. Add Quantity: Our 10 concurrent users, remember to modify the number of threads, because the number of threads can lead to inadequate collection point, a collection of never less than adequate number of users, concurrent.

 

 

 4. Click Run, you can view the results of the tree, the result is sudden.

 

Guess you like

Origin www.cnblogs.com/mawenqiangios/p/11608341.html