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 -


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?

Popular posts from this blog

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

Verify email confirmation using Selenium

Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can

Return only first or last element from webelements collection

We often come across situation when there are multiple elements on a page and we probably like to exercise only a few of them using selenium webdriver. May be just first and last element. For example on a search result page we may like to click on only first and last link and not all. This is when Iterables API comes handy. (By the way I am assuming that you have already completed watching selenium training videos :)). Once we have collection of web element then we can use Iterables to get only first or last element as following - Consider that we fetch collection of element as - List< WebElement > webElements = getDriver().findElements(By. id ( "htmlID" ));   Now we can get the first web element from this collection as -  WebElement firstElement = Iterables. getFirst (webElements,  getDriver().findElement(By. id ( "defaultElement" )));   Herein second argument -   (getDriver().findElement(By. id ( "defaultElement" )))    in the me