For our load test we will use the following setup:
User-Defined Variables:
Parameter Name | Description | Value |
host | URL component 'host' of application being tested (URL or IP). | jmeter.loc |
admin_password | Admin backend password. | 123123q |
loops | Number of loops to run. | 5 |
frontendPoolUsers | Total number of Frontend threads. | 100 |
adminPoolUsers | Total number of Admin threads. | 20 |
csrPoolUsers | Users of Customer Support Request (CSR) Pool | 20 |
customer_password | Frontend Customer password | P@ssword123 |
Frontend Pool
Catalog Browsing by Guest
Catalog Browsing by Customer
Add to Cart by Guest
Add to Cart by Customer
Checkout by Guest
Checkout by Customer
Account management
Admin Pool
Browse Product Grid
Browse Order Grid
Admin Create Product
Admin Edit Product
CSR Pool
Admin Returns Management
Browse Customer Grid
Admin Create Order
Also we need to set the percentage of performing threads, for example - 70%
For real-world load testing, the command line option should be used, as it requires significantly fewer resources. Additional parameters will be taken from benchmark.jmx testplan
./jmeter -n -t benchmark.jmx -j ./jmeter.log -l ./jmeter-results.jtl
Reading results with JMeter GUI
Open the JMeter application in the GUI mode with the following command in the same ~/apache-jmeter-5.5/bin/ directory but without any parameters.
./jmeter
JMeter supports a number of ways to view the test results such as the Aggregate Report, Results Tree, and Graph Results.
You can open the saved test result file (jmeter-results.jtl) by clicking the Browse button for example in the Aggregate Report. Aggregate Report contains collected information about all of the requests including counts, min, max, average, error rate, and approximate throughput.
