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 -
This is how page html looks -
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?