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

Using xPath to reach parent of an element

Note: If you are new to java and selenium then start with selenium java training videos .   I prefer css locator over xPath but there are times when css locators don't fit requirement. One such requirement is when you want to navigate to parent element of an element and may be parent of parent and even more. Unfortunately css locators don't provide any mechanism to navigate to parent of an element. See this for more. Of late I came across a scenario when I wanted to click on a link depending upon the text in a text box. Herein parent of text box and parent of link were at the same location. More over there could have been many such combinations in application. Fortunately I just need to pick first such instance and Web Driver any way considers only first instance when multiple locators are found matching an element. Element in question is in following html - Here I need to click on highlighted anchor on the basis of input element (which is also hig...

Verify email confirmation using Selenium WebDriver

Note: If you are new to java and selenium then start with selenium java training videos .   How to Verify Email Confirmation Using Selenium 4 and JavaMail (2026 Guide) Email confirmation is a critical part of most registration flows — account activation, password reset, multi-factor authentication, and onboarding. Every automation engineer eventually faces the same challenge: How do you verify an email confirmation link inside a Selenium test without making it slow and flaky? The wrong instinct is to automate Gmail's UI with Selenium. It's fragile, slow, and breaks constantly. The right approach: Use Selenium for browser automation Use JavaMail (IMAP) to read the email directly Extract the confirmation link Continue the test in Selenium Why Not Automate Gmail UI With Selenium? Automating the Gmail UI means logging in, searching, clicking a message, and parsing content from a third-party interface that changes frequently. This leads to: Flaky...

Real Time JMeter Result Using Backend Listener

Since JMeter 2.13 Backend Listener has been available to create real time graph of JMeter Test. Following tutorial explain the entire process in detail. At the end of this tutorial you would be able to create JMeter Live Test Result dashboard similar to following - This tutorial borrows information from many sources and my own experiments with JMeter live reporting dashboard. I have added source of information wherever applicable But before we can build such a snazzy JMeter Live Reporting dashboard we need to understand two more components - influxDB (a time series database) and Grafana Dashboard This is a big tutorial, so take deep breath :-) and follow on. Once you complete set up specified in this tutorial then you can watch JMeter Training Video Tutorial to watch this in action. What is Time Series Database? A time series is a sequence of data points , typically consisting of successive measurements made over a time interval . Examples of time ...