JMeter Web launcher (jmeter_web.jar)

The JMeter Web launcher allows running load testings on web sites.
It has been tested with JMeter v2.4.


Configuration

The jmeter_web.xml file allows pre-configuring the launcher with some default values:


Parameter Description
General
Java install path This must indicate the path to the java install.

Default value is: C:/Program Files/Java/jdk1.6.0_17
Test root path This must indicate where are located all the JMeter tests.
This is a root path. Each test in XStudio has a canonical path that will be appended to this path.
This path MUST not include an ending slash.

Default value is: C:/test_repository/tests/jmeter
Connection timeout (seconds) This must indicate the connection timeout value.

Default value is: 30
Request timeout (seconds) This must indicate the request timeout value.

Default value is: 30
Acceptable failure rate (%) This must indicate the acceptable failre rate.

Default value is: 0
Nb simulated users This must indicate the number of simulated users.

Default value is: 100
Time to reach max load (seconds) This must indicate the time to reach the max load.

Default value is: 60
Nb requests per user This must indicate the number of request sent per user.

Default value is: 3
Nb values to compute max time This must indicate the number of values measured to calculate the request max time. By default, the declared max time will be the average of the 3 biggest times.

Default value is: 3
JMeter
JMeter install directory This must indicate where JMeter has been installed.

Default value is: C:/jakarta-jmeter-2.4
Temporary folder This must indicate the path of a folder where we are going to store temporary data.

Default value is: C:/WINDOWS/Temp


These values can be changed while creating the campaign session from XStudio.


Requirements

The launcher will first take care about running the JMeter server. Do NOT run the server by yourself.
The tests must be named with the extension .web and contain description of command executed on the website.


For instance:
url=http://192.168.10.104/index.html port=8080
method=POST
param=login value=johndoe
param=password value=foobar
param=request value=account
url=http://192.168.10.104/index.html port=8080
method=GET
param=login value=johndoe
param=password value=foobar
param=command value=33552422
url=http://192.168.10.104/view_command.php port=8080
method=GET
param=login value=johndoev param=password value=foobar
param=command value=34620263



The JMX tests are generated dynamically from these tests and executed by the launcher.
At the end of the test execution, a chart is generated by the launcher based on the JTL results produced by JMeter and uploaded to XStudio. All the logs are also attached to the testcase execution in XStudio. The test will be marked as passed or failed depending on the failure rate measured by JMeter.


Tutorial: Creating and executing JMeter Web tests

In this tutorial, we will learn to run some JMeter load tests.


Prerequisites

Install JMeter in the folder C:\jakarta-jmeter-2.4
Create a file Test1.web in the folder C:\test_repository\tests\jmeter\folder1.
Open this file and copy the following in it:
url=http://192.168.10.104/index.html port=80
method=POST
param=login value=johndoe
param=password value=foobar
param=request value=account
url=http://192.168.10.104/index.html port=80
method=GET
param=login value=johndoe
param=password value=foobar
param=command value=33552422



Create a dedicated category for JMeter Web tests and create a test

  • create a category JMeter SQL associated to the launcher jmeter_web.jar
  • under this category, create (somewhere in the tree) a test with name Test1 and with a canonical path set to folder1.



Creating a test campaign

  • create a campaign including only the test Test1
  • create a campaign session using a configuration having all the default values.



Run a campaign session

Run the campaign session


After the session's execution is completed, you can look at the results from XStudio:
  • the messages indicate the failure rate and the average time to execute the queries
  • you can also check that all the log files (including the JMX, the JTL and the log files) are attached as well as a chart which looks like: