Performance testing with Jmeter

This post attempts to explain the basic design, functionality and usage of Junit Sampler for Jmeter. The sampler was introduced in 2.1.2 release of Jmeter. Earlier releases do not have the sampler. Design The current implementation supports standard Junit convention and extensions, like oneTimeSetUp and oneTimeTearDown. Other features can be added on request. The sampler works like the JavaSampler with some differences. 1. rather than use Jmeter's test interface, it scans the jar files for classes extending junit's TestCase class. This means any class or subclass. 2. Junit test jar files are copied to jmeter/lib/junit instead of jmeter/lib 3. Junit sampler does not use name/value pairs for configuration. The sampler assumes setUp and tearDown will configure the test correctly. Note: setUp and tearDown methods must be declared public, so that Jmeter can use it. 4. The sampler measures the elapsed time only for the test method and does not include setUp and tearDown

We all know that the word Automation means, there should not be any human intervention for the task. Similarly w.r.t Jmeter we can achieve this by integrating with the ant build process. When ever a new code is checked in and build has happened then Jmeter should kick off immediately, run the scripts and produce the performance report, So now the question is how to do this? Answer is simple, 1.To use the task, you must have JMeter installed. You must also include ant-jmeter-1.0.9.jar in your Ant classpath. Adding the jar to $ANT_HOME/lib will make this happen automatically. 2.Set the jmeterhome parameter to your JMeter install location, and the resultlog parameter to the name of a file to log the test results to. You can either specify a single test plan using the testplan parameter, or multiple test plans using the testplans nested element. The testplans element is a standard Ant FileSet element. This is an Ant task for automating running JMeter test plans. The task execu