Please post your Web Driver questions in official Web Driver forum

Saturday, April 30, 2016

How to handle duplicate element locators?

Have you come across use cases when you have create multiple element locators for almost similar element locators?
Consider following text box, which gets date filled when user clicks on - expired, today, end of week etc links -

Screenshot from 2016-04-30 21:49:18.png

This is how page html looks -

Screenshot from 2016-04-30 21:56:44.png

And the element locators for expired, today etc link could be -


There are other possible element locators but each link requires its own element locator.
Now considering earlier example, the only difference in element locator is index number 1, 2 etc

So what if we could get rid of creating different element locators and pass index number depending on the link we want to interact with?

Let’s create base element locator -

private static LinkElement getExpiryLinkElement(int index) {
  return new LinkElement("Expired Link",
          By.cssSelector(String.format("#coupon_expiryAt~a:nth-of-type(%s)", index)));

Let’s set up an enum for expired, today etc links -

public enum ExpiryDate {

And a method which returns element locator corresponding to expired, today etc links

private LinkElement getExpiryLink(ExpiryDate expiryDate) throws Exception {

  switch (expiryDate) {

  case EXPIRED:
      return getExpiryLinkElement(1);

  case TODAY:
      return getExpiryLinkElement(2);

  case END_OF_WEEK:
      return getExpiryLinkElement(3);

  case MONTH:
      return getExpiryLinkElement(4);

  case NEXT_MONTH:
      return getExpiryLinkElement(5);

  case YEAR:
      return getExpiryLinkElement(6);

  case ONE_MONTH:
      return getExpiryLinkElement(7);

      return getExpiryLinkElement(8);

  case SIX_MONTH:
      return getExpiryLinkElement(9);

  throw new Exception("Invalid expired Link");


Method to select expiry date would be -

public PageObject selectExpiryDate(ExpiryDate expiryDate) throws Exception {
  return this;

Now test method could set any of the expiry date as -



and so on...

What do you think of this approach which gets us rid of creating 9 element locators? How would you have approached it?

Sunday, April 17, 2016

Should you be using Distributed Testing for Performance Testing ?

Having posted elaborately on how to carry out JMeter distributed and using Jmeter Backend listener to plot live graph of running test. I have been disappointed with entire approach. And my disappointment is not limited to just JMeter as any other performance testing tool would suffer from similar factors.

Distributed test itself results in lower throughput than what you can achieve from test running from independent machine. This is described on (unfortunately web site is down for quite some time). I am pasting the reasoning here -

  1. If you want to use your local machine to control the test you have to navigate the joyous process of getting RMI to work over multiple subnets and firewalls to allow your local machine to control multiple remote (EC2) slaves – you can do this by tunnelling RMI communication and patching JMeter, it’s messy though. To workaround this issue you have to use a remote Master as well as remote Slaves.
  2. Even then, in master/slave mode when running high throughput tests JMeter will eventually reach an IO or network bottleneck that will affect the results (even using Batch mode). Too many processes trying to write to a single file at the same time inevitably start to queue. To be certain of avoiding this issue you have to not use Distributed mode and instead run multiple independent tests over n hosts that do not use the GUI and do not write results to a single master but instead run at the command line and keep results local. Then, after the test is complete, you have to collate everything. This approach has several annoying problems: a) excessive terminal windows, b) limited visibility on test progress as it happens, c) to preserve throughput the jmx file must be adjusted for the number of hosts in use and d) too much time is spent on repetitive tasks that could be automated.
I myself encountered weird issue of sudden drop in application throughput when using JMeter Distributed test on aws. But when I executed test independently on various machines then the issue never surfaced.

Not just this, using backend listener on distributed mode causes more drop in application throughput than what you can achieve with just distributed mode.

Given these reasons I decided to gave up on using distributed mode and backend listener entirely and began to use JMeter-EC2 project. Since the original project is not compatible with latest JMeter version I ended up forking it and using my own version. You could try it and it is compatible with JMeter 2.13

Now this leaves us on how we can yet use snazy grafana dashboard. The way to approach this would be to directly push results to influx db either from summary report or from jtl files. Something have not yet explored, have you?
Fork me on GitHub