In my previous blog, I have explained about basic “Thread Group” element which comes with Apache JMeter package by default. Basic Thread Group element has certain limitations, such as if you want to do spike test then you can not create such workload in the basic thread group. There are some external plug-ins are available which can help a performance tester to achieve his performance goal by creating the desired workload. I found one of the best “Ultimate Thread Group” which can help you to overcome from basic Thread Group limitations. Using Ultimate Thread Group you can apply conditional load on the server.
How to download “Ultimate Thread Group” plug-in?
1. Click on the link to download Ultimate Thread Group JMeter Plugin
2. Unzip the folder
3. Copy the file jmeter-plugins-cmn-jmeter-<version>.jar to lib folder of Apache JMeter
apache-jmeter-<version> –>lib –> Paste jmeter-plugins-cmn-jmeter-<version>.jar
4. Copy the files jmeter-plugins-casutg-<version>.jar and jmeter-plugins-manager-0.10.jar to ext folder of Apache JMeter
apache-jmeter-<version> –>lib –>ext -> Paste jmeter-plugins-casutg-<version>.jar and jmeter-plugins-manager-<version>.jar
That’s it!
Please note .jar file version may change as per plug-in update.
Please note .jar file version may change as per plug-in update.
How to open/add “Ultimate Thread Group” in Test Plan?
1. Select "Test Plan" node
2. Right click on "Test Plan" node
3. Mouse hover "Add"
4. Mouse hover "Thread (Users)"
5. Click "jp@gc – Ultimate Thread Group"
How to configure Work Load using “Ultimate Thread Group”?
1. Once the Ultimate Thread Group is added the page will look like below GIF
2. Click on Add Row button to add more rows for different number of users
3. I am going to add 6 Rows for the users 10, 20, 30, 100,100,100,100 . So totally 460 users
4. Please refer to the configuration given below
How to remove “Ultimate Thread Group”?
2. Right click on "jp@gc – Ultimate Thread Group" node
3. Click "Remove" (Mouse) or "Delete" button from keyboard
4. Click "Yes"
What are the attributes of “Ultimate Thread Group”?
a. Name: To provide Thread Group name. It may be your Test Case/Test Scenario name
b. Comments: To provide comments
c. Action to be taken after a Sampler error: Actions taken in case of sampler error occurs, either because the sample itself failed or an assertion failed etc. The possible choices are:
i. Continue - ignore the error and continue with the test
ii. Start Next Loop - ignore the error, start next loop and continue with the test
iii. Stop Thread - current thread exits
iv. Stop Test - the entire test is stopped at the end of any current samples.
v. Stop Test Now - the entire test is stopped abruptly. Any current samplers are interrupted if possible.
d. Thread Schedule: Number of users to simulate.
1. Start Thread Count: The count of threads for a particular time slot.
2. Initial Delay: Initial delay is the time for the first user (thread) to hit the server after JMeter starts. This time is nothing but just after how many seconds you want to hit the server first time.
3. Start-up time: Start up represents ramp-up time and it divides among each user. If you have 10 users and 60 seconds as Start-up time then next user will be started at next 6th second. Likewise:
1st user at 6th second
2nd user at 12th second
3rd user at 18th second
.
.
.
10th user at 60th second
4. Hold Load For: It represents a steady state of Work Load Scenario.
5. Shutdown Time: It represents ramp-down time. same concept as Start-up time.
Stepping Thread Group
Ultimate Thread Group
Related Topics:
No comments:
Post a Comment