Skip to main content

XPath and single quotes


I had tough time dealing with XPath and single quote. Though W3C recommends using ' to escape it but I never got it working, let me know if any of you get through.
Came across this blog and found that “concat” could be used in this situation.
So original XPath expression is –

//meta[@name=’DESCRIPTION’][@content=’Tester’s Test’]

This is some thing which certainly fails as single quote in “Tester’s” marks it at end of string and then XPath blows up, next trial was –

//meta[@name=’DESCRIPTION’][@content=’Tester''s Test’]

This does not work despite w3c recommendation!

And then I used concat function and split the string as –

concat(‘Tester’,”’”,’s Test’)

NOTICE that single quote is kept in double quote while other characters are kept in single quotes.
So XPath looks as –

//meta[@name=’DESCRIPTION’][@content=concat(‘Tester’,”’”,’s Test’)]

And this works charm.



Comments

  1. Thanks for the post, it's helping me out.

    I'm trying to write a similar Xpath, in Google Docs, to pull only the meta descriptions off web pages.

    I feel your example is getting me close...but I'm not there yet!

    Any ideas on what it would look like?

    Thanks!

    ReplyDelete
  2. Glad you liked it.

    For meta tags you could use XPath like -

    //title[text() = 'title text']

    //meta[@name='keywords'][@content='jobs, web, testing']

    But I suggest to use CSS insead..

    ReplyDelete

Post a Comment

No spam only genuine comments :)

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