Skip to main content

Selenium Training Meet 19th May - Video Recording

Just finished first on line Selenium meeting. There were about 120 registration received and more than 60 users participated in meeting which does not seem bad for a meeting held on weekend. Meeting recordings can be watched here. Feel free to share in your contacts.

A few of you complained about audio unavailability. If you are not able to hear audio then please reload/refresh the video URL.

The meeting was largely focused on xPath and CSS locators. If you participated in meeting and have an opinion/suggestion then please post it here

A few of you asked me to post questions I asked towards end of session. They are -

  • How to use "ends-with" with xPath
  • How to use nested predicate with xPath
  • Finding nth child in css selector

We should also thank anymeeting for the wonderful resource they provided for on line meet. Stay tuned for next meet.


  1. Tarun, there is no voice. Can you please check?

    my speaker working fine.

    1. I checked on Chrome Browser and it works. Could you try once again.
      There was one instance when I could not hear audio. That may have been technical issue with Anymeeting. Let me know if it does not work for you at all.

      Also try loading video in incognito window of chrome (ctrl + shify + N), in case your add on are causing trouble.

    2. Sonali, Please see the post again, I have updated it about audio unavailability and corresponding trouble shoot.

  2. Thanks a lot Tarun. Great session and great initiative, watched the recording this time, will try to participate for the next one.

    Guys regarding audio, I too faced some issues initially, finally the workaround was to use IE8 and refresh it when u couldn't hear the sound. You could move the recording to where you finished earlier and it works fine


Popular posts from this blog

Where is my defect ID?

Don't you feel ecstatic when your automated tests find bug? After all tests finding bugs give us a sense of accomplishment, is not it? And this is followed by usual cycle of defect reporting, retesting and hopefully closure of defect. But at times defects are deferred to next or future releases. Which causes test method to fail for subsequent releases. And if you are dealing with a test suite having 100s of tests then it may become difficult to remember if there was a defect reported for a failing test? How do you deal with such situation. How about adding defect-id to @description tag of TestNG test. Hence it is reported on automated test report and we would know if defect exists for a failing test - How do you track defect-id of a failing test?

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

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