Message-ID: <486481198.14632.1406653141494.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_14631_339905574.1406653141494" ------=_Part_14631_339905574.1406653141494 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Description / Features
This plugin collects performance tests results from Apache J= Meter. Apache JMeter may be used to test performance bo= th on static and dynamic resources (files, Servlets, Perl scripts, Java Obj= ects, Data Bases and Queries, FTP Servers and more). It can be used to simu= late a heavy load on a server, network or object to test its strength or to= analyze overall performance under different load types. You can use it to = test your server/script/object behavior under heavy concurrent load.
If it is the first time you have heard of Apache JMeter = then you should try it before using this plugin.
The following metrics are recorded in SonarQube:
If you want to use JMeter Report Server then:
Run the server where your JMeter instance is running:
JMeter installation is very easy. JMeter is developed with Java and it i= s distributed as a compressed file.
You can download it from http://jakarta.apache.org/jmeter= and then run the provided script (bin/jmeter).
You can find a step by step tutorial in JMeter's website: http://jakarta.apache.org/jmeter/user= manual/jmeter_proxy_step_by_step.pdf
It describes how to record a test plan using the JMeter proxy.
You can also take a look at this video tutorial to see how to record a t= est with JMeter:
The SonarQube JMeter plugin uses the results datafile generated by = JMeter (file with extension .JTL) so remember to configure your test plan t= o store the results in a single JTL file.
In this video we show you how to set this JTL file:
JMeter Report Server is a server that generates performance reports from= JMeter results. The SonarQube JMeter Plugin uses this server to get t= he performance metrics from the projects.
It must be installed on the same machine with JMeter tool. The server wi= ll read the JTL files to provide all the data to SonarQube.
JTL files must be provided as a result of JMeter tests. The JMeter Repor= t Server is needed just to make JTL files available remotely.
JMeter Report Server needs to know where the JTL files are located. You = can set your test configuration when running the server through command lin= e system properties:
where name is the test configuration that you will use in SonarQube JMet= er Plugin project settings.
Or you can also set this location by creating a property file "jmet= er-report-server.properties" with all your test configurations:
This is useful if you have multiple projects in your JMeter environment = and you want to manage all your tests with a single JMeter Report Server.= p>
Port and maxConnections are now configurable properties and they can be = set as system properties (using -D in the start command) or as normal prope= rties in the jmeter-report-server.properties file as shown below.
Here you have a test configuration example:
This configuration will set JTL file "/home/carlos/jmeter_work/icew= eb.jtl" to the project "iceweb".
"iceweb" will be the name for your test configuration. So= narQube plugin settings will use that name.
Server is package in a single jar with all dependencies, so just downloa= d JMeter Report Server and put it wherever you want
You can start the server with this command:
NOTE: replace "jmeter-report-server.jar" with the name of the = file downloaded and testconfig property with your project name and the path= to the JTL file.
This video shows how to configure JMeter plugin in SonarQube:
Since version 0.2, there is a jmeter-report-server embedded inside the S= onarQube JMeter plugin, and there is a new configuration option (Loca= l jtl file) where you can set a jtl file path, local to the sonar server. I= f this option is set, no remote jmeter report server is used, and jmeter te= st results are taken from the local file.
Now it is possible to configure units of time in your global or project = settings. You can set seconds, minutes or hours.
Add the JMeter widget to your dashboard and next time you run
sonar:sonar you will retrieve performance metrics from JMeter, and S=
ONAR will show them.
You have to configure your project to be able to do that:
To get sonar-jmeter-plugin working in maven side, there must not be any = configuration values set in SonarQube (all of them must be blank).
||SON= ARPLUGINS-1339=20||Apache JMeter 2.5 = support=20||=20|
||SON= ARPLUGINS-1274=20||Allow to set jtl p= ath as a classpath path=20||=20|
||SON= ARPLUGINS-1271=20||Sometimes sockets = are not closed in the server=20||=20|
||SON= ARPLUGINS-1270=20||Limit the number o= f connected clients=20||=20|
||SON= ARPLUGINS-1259=20||Allow jmeter-repor= t-server port to be configurable=20||=20|
||SON= ARPLUGINS-1198=20||Implement JMeterPo= stJob for getting performance metrics in maven side parsing reports generat= ed by maven-jmeter-plugin=20||=20|
||SON= ARPLUGINS-1018=20||Configuring unit <= /a>=20||=20|
|=20||SONA= RPLUGINS-984=20||Add an option to us= e sonar-jmeter-plugin without JMeter Report Server=20||=20|
|=20||SONA= RPLUGINS-983=20||Update documentatio= n=20||=20|
|=20||SONA= RPLUGINS-982=20||Plugin usability: c= ommand line parameter for JTL file=20||=20|
|=20||SONA= RPLUGINS-956=20||Code best practices==20||=20|
|=20||SONA= RPLUGINS-913=20||Plugin documentatio= n=20||=20|
|=20||SONA= RPLUGINS-906=20||Upload code to SVN ==20||=20|