Jmeter

Jmeter is the best available open source tool used for load testing. Lots of users are working on it and it provides almost all features that any good load testing tool provides. It doesnt provide flashy UI , but its gives you robust tool o collect information on performance of your application, and that too for free. http://jakarta.apache.org/site/downloads/downloads_jmeter.cgi Binary --- Download Zip file from there Install jdk System Properties --> Advance -->Environment Variables Variable Name : %CLASSPATH% Variable Value :JMETER_HOME Variable Name : JMETER_HOME Variable Value :c:\Jmeter For Web service (SOAP) Request download mail.jar from link below to lib folder http://www.java2s.com/Code/Jar/m/Downloadmailjar.htm Also download activation.jar from link below to lib folder http://www.java2s.com/Code/Jar/a/Downloadactivationjar.htm Getting Started: Run-->cmd -->cd jmeter\bin -->jmeter Logs available at C:\jmeter\bin:jmeter.log Two things available at that point Test Plan WorkBench User manual and details on each component is available at http://jakarta.apache.org/jmeter/usermanual/index.html Using Jmeter efficiently If we divide load testing into 3 parts: 1. Recording ( Script generation) There are there different ways to generate script: a) Manually find out from the application code what all values are being send to server and there variable names and place them in Jmeters Test Plan --> Thread Group --> Sampler --> ( Ex. HTTP Request) b) Record application using Proxy server (supports only HTTP), to know detail read following document: http://jakarta.apache.org/jmeter/usermanual/jmeter_proxy_step_by_step.pdf c) The easiest way is to use third party tool Badboy for recording. http://www.badboy.com.au/ Download this tool, and install its temporary license version. Record the script, and once finished recording, go to File in Badboy, and chose option Convert it to Jmeter Script. It will generate .jmx file which can be open up in Jmeter. Note: Scripts generated using this tool will contain some garbage values, run the script once and identifies the failure, and remove that garbage code. Basic folder structure design for Jmeter:

C:\>cd myportal C:\myportal>tree Folder PATH listing bin jmeter data docs result script ReadMe says: bin folder should contain the jmeter tool itself. data folder contains all input data, including username/passwords, any attachment of files etc. docs folder contains some reference document, including reports document result folder contains output data stored during run time. We should specify this path in all Listeners to store data for future reference and result creation after the Load test. script contains actual .jmx file