Skip to main content

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 -


"#coupon_expiryAt~a:nth-of-type(1)"
"#coupon_expiryAt~a:nth-of-type(2)"


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 {
  EXPIRED, TODAY, END_OF_WEEK, MONTH, NEXT_MONTH, YEAR, ONE_MONTH, THREE_MONTH, SIX_MONTH;
}


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);


  case THREE_MONTH:
      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 {
   getExpiryLink(expiryDate).click();
  return this;
}


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


selectExpiryDate(ExpiryDate.EXPIRED)
Or


selectExpiryDate(ExpiryDate.TODAY)


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?

Popular posts from this blog

Distributed Load Testing with JMeter

Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred

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

XPath and single quotes

I had tough time dealing with XPath and single quote. Though W3C recommends using ' to escape it but I never got it working, let me know if any of you get through. Came across this blog and found that “concat” could be used in this situation. So original XPath expression is – //meta[@name=’DESCRIPTION’][@content=’Tester’s Test’] This is some thing which certainly fails as single quote in “Tester’s” marks it at end of string and then XPath blows up, next trial was – //meta[@name=’DESCRIPTION’][@content=’Tester''s Test’] This does not work despite w3c recommendation! And then I used concat function and split the string as – concat(‘Tester’,”’”,’s Test’) NOTICE that single quote is kept in double quote while other characters are kept in single quotes. So XPath looks as – //meta[@name=’DESCRIPTION’][@content=concat(‘Tester’,”’”,’s Test’)] And this works charm.