Skip to main content

Test Java class with JMeter

It is quite easy to test API or Website using JMeter but you may come across situation when you have to load test java class directly. This post described how a java class can be load tested. We will write a java program and use JMeter Java Sampler to load test it. 

  • Set up a maven selenium project. If you are new to java and maven then you may like to check my java tutorials
  • Add following dependencies to your maven project - 
<dependency>
    <groupId>org.apache.jmeter</groupId>
    <artifactId>ApacheJMeter_core</artifactId>
    <version>3.1</version>
</dependency>
<dependency>
    <groupId>org.apache.jmeter</groupId>
    <artifactId>ApacheJMeter_java</artifactId>
    <version>3.0</version>
</dependency>

  • Let's write a java program to add numbers - 

public class AddNumbers {

    public int addTwoNumbers(int a,int b) {

        return a+b;
    }
}

  • And a test program which we would use in JMeter later on.
  • Implement interface JavaSamplerClient or to extend AbstractSamplerClient.
  • You can leave other methods empty and would have to implement runTest and getDefaultParameters. The test class would look as -

public class AddNumberTest implements JavaSamplerClient {

    @Override public void setupTest(JavaSamplerContext javaSamplerContext) {
    }

    @Override
    public SampleResult runTest(JavaSamplerContext javaSamplerContext) {

        String var1 = javaSamplerContext.getParameter("var1");
        String var2 = javaSamplerContext.getParameter("var2");

        SampleResult result = new SampleResult();
        result.sampleStart();
        result.setSampleLabel("Test Sample");

        // Test Code
        AddNumbers addNumbers = new AddNumbers();
        if(addNumbers.addTwoNumbers(Integer.valueOf(var1), Integer.valueOf(var2))==2) {
            result.sampleEnd();
            result.setResponseCode("200");
            result.setResponseMessage("OK");
            result.setSuccessful(true);
        } else {
            result.sampleEnd();
            result.setResponseCode("500");
            result.setResponseMessage("NOK");
            result.setSuccessful(false);
        }

        return result;
    }

    @Override public void teardownTest(JavaSamplerContext javaSamplerContext) {

    }

    @Override public Arguments getDefaultParameters() {
        Arguments defaultParameters = new Arguments();
        defaultParameters.addArgument("var1","1");
        defaultParameters.addArgument("var2","2");
        return defaultParameters;
    }
  • getDefaultParameters has the parameters with default values. This values would appear on Java Sampler which we
  • would see later on. runTest method uses the parameters supplied from getDefaultParameters. runTest is quiet 
  • simple. It add given numbers, if sum is equal to 2 then it is a success else failures.

  • Now package your project using mvn package and place the generated jar file in JMeter's following directory -
  • ~/apache-jmeter-3.0/lib/ext/
  • Now open JMeter and add Java sampler and select classname as AddNumberTest -





  •  Lets run the test with default variables and you will see it fails since 1+2 is not equal to 2 - 


  • Let's change default values to 1 - 




  • Let's run test again and it is green now - 


  • Now you can set up your test with required thread, duration and other parameters :)

** When you create new jar then you should restart JMeter. I did not see JMeter picking changes after placing new jar in /lib/ext/ directory and not restarting the JMeter

Popular posts from this blog

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

Security Testing and Selenium

I have come across many articles which talk of carrying out security testing with selenium however I found it very cumbersome to set up such tests. This is what this tutorial is going to make easy for you. It cover. My next Security Testing and Selenium YouTube video covers following - Importance of having security testing on CI What is dynamic application security testing Recommended tools from https://owasp.org/www-community/Vulnerability_Scanning_Tools What is https://owasp.org/ ?   Using https://www.zaproxy.org/    Project setup  <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap-clientapi </artifactId> <version> 1.9.0 </version> </dependency> <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap </artifactId> <version> 2.10.0 </version> </dependency> Start ZAP daemom (headless) mode  ./zap.sh -daemon -host 127.0.0.1 -port 8080 -config api.addrs.a

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro