Please post your Web Driver questions in official Web Driver forum

Sunday, May 13, 2018

Become an Author

Do you want to share you testing expertise with other?
Do you want to let others know how you tested that complex module either though manual testing or in automated manner?
Then become an author at seleniumtests.com, drop me a line at tkumarb at gmail dot com and let's spread the knowledge together.

Sunday, July 23, 2017

Do you check for absence of element on page

When writing automated tests we often check presence or absence of element for assertion conditions. This is usually written as - 

assertTrue("Element is missing. Bug!!!", pageObject.isSomeElementDisplayed());

And when element is not displayed then above mentioned assert statement fails.

In the similar manner we can write following assert statement to check for absence of element - 

assertFalse("Element is present. Bug!!!", pageObject.isSomeElementDisplayed());

Above mentioned assert statement would fail if element is displayed on page.

Everything looks ok, is not it. Not really, there is catch. Let's have a closer look at assertFalse statement we used above - 


assertFalse("Element is present. Bug!!!", pageObject.isSomeElementDisplayed());

This assert statement would also succeed even if webpage results in 404/500 or any other error page, since error page would also be missing the element on which we are performing assert.

So what is the solution? My recommendation is to not use check for absence of element but presence of element for assertion. What do you think of this approach?

Sunday, February 26, 2017

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
Fork me on GitHub