Forum Discussion

enriquebravo's avatar
enriquebravo
Contributor
3 years ago

Using regexp for FindElement

Hello,   I read several other forum post similar to my issue and seems like regexp and FindElement may not work.   I got the following dynamic xpath: FindElement("//div[@id='__49_0']//input") Unf...
Keyword Tests
Object Recognition
web testing
  • chriscc's avatar
    chriscc
    3 years ago

    Hi enriquebravo,

     

    I am not a xpath expert...if the id number is dynamic, and id isn't unique to that div element, then you shouldn't have to look for the id attribute in your expression.  Something like  this might work: FindElement("//div//input")

     

    if the id is unique to that div element then you can simply verify that it exists, something like this might work:  FindElement("//div[@id]//input")

     

    if part of the attribute is unique, like the underscores, then you might be able to use the contains method, like this:  FindElement("//div[contains(@id, '__')]//input")

     

    Not sure if any of this works or helps, but I thought I'd share.  

AlexKaras's avatar
AlexKaras
Champion Level 3

Hi,

 

Documentation for .FindElement() does not mention possibility to use regular expressions, so I am far not sure that it will work. Another consideration to support this thought is that .FindElement() was introduced with cross-platform web testing and seems to transfer all calls to Appium under the hood. Thus, as Appium does not support regexp for XPath/CSS selectors, likewise .FindElement() does not.

 

> when using the Find methods, only xpath 1.0 is supported 

Correct. This is documented in the article for FindElement.

 

> when the FindElement method is successful, does it automatically click on the object?

No. Just a found element is returned and it is up to your test code to do what is required with the found element (click it, drag it, use it as an anchor for the next search, etc.).

 

enriquebravo's avatar
enriquebravo
Contributor
3 years ago

Hey Alex,

 

So my understanding is that using regexp is not much of an option when specifying selector values. I guess it is a drawback of using xpaths or css selectors instead of the good-old object properties. I had a similar issue with a Logout link, which I would think is easy to identify but it wasn't the case. There is a dependency on the parent object page. I was trying to find a way how to make it "page-independent", but I couldn't as the object relies on xpath.

 

Thanks for your note and for looking into it. I ended up using SendKeys and it works ok. Will see if there are other options in the future.

 

Regards,