Skip to main content

Return only first or last element from webelements collection

Note: If you are new to java and selenium then start with selenium java training videos. 

 
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 method getFirst is the default element which would be used 
when collection is empty. Once we have control of "firstElement" 
WebElement then we can click on it or use various other WebDriver
methods 
 
And we can get the last element from collection as - 
 
WebElement lastElement = Iterables.getLast(webElements, 
getDriver().findElement(By.id("defaultElement")));
 
Here again, second argument of method getLast is default element
 
So next time you want to exercise only first and last element from
a collection of web element then you can use these handy APIs and not
any weird loop. Stay tuned for more test automation tips :)

Comments

  1. Good tip. Although couldn't you just do this as well?

    WebElement firstElement = webElements.get(0);
    WebElement lastElement = webElements.get(webElements.size()-1);

    And another option, if ok to use XPath, is to use XPath to specifically define the n-th element in the collection that you are matching against for value that returns multiple matches. That way, it won't needlessly return the whole set when you won't be using the rest. This is also helpful when you are already using XPath. Example

    WebElement firstElement = driver.findElement(By.xpath("(//someXPathThatMatchesMultipleElements)[1]"); //returns 1st element
    WebElement lastElement = driver.findElement(By.xpath("(//someXPathThatMatchesMultipleElements)[n]"); //returns nth element, if you knew what last element n value would be

    ReplyDelete
    Replies
    1. could use the 0 and works too thought solution does not seem so comprehensible at first, is not it? :-)
      on xPath, I give preference to other element locators over xPath because of its slowness. Also it is not always straight forward to use [n] locator with xPath.

      Delete

Post a Comment

No spam only genuine comments :)

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...

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -

Should selenium tests be always independent? The endless debate !!

Though unit tests have always recommended to be independent of each other, advent of selenium+TestNG has given birth to dependent integration/end to end tests. TestNG Author Cédric Beust had written about it few years ago. When I had begun writing selenium tests I used to launch browser once in one test class and test methods were usually dependent on one another. Hence 2nd test method would begin test run on same browser + application state where 1st test method stopped. Launching just one browser for five or more test methods in a class is big time saving is not it? Well not really, for the reasons I am going to describe in this post. Since then I have moved on to launching browser per test method but yet give in “charm” of dependent test methods at times. to So here are the few pros and cons for dependent tests and - Pros - Similar steps of execution don’t have to be repeated in multiple tests when steps constitutes a test method in themselves If login fails then...