Page 1 of 1

Can you explain why eValid is better than XPath?

PostPosted: Wed May 11, 2016 11:25 am
by RGarrett
Afternoon.

Interesting reading on this forum.

In an earlier post back in April, you explained how you handle something that seems to be
mid-way between an XPath and a Regular Expression.

Here is the link from that particular forum post in question:

viewtopic.php?f=18&t=33253&p=49871&hilit=XPath#p49871

Can you explain why is your solution better?

Thanks

Re: Can you explain why eValid is better than XPath?

PostPosted: Thu May 12, 2016 2:06 pm
by eValid
RGarrett wrote:Afternoon.

Interesting reading on this forum.

In an earlier post back in April, you explained how you handle something that seems to be
mid-way between an XPath and a Regular Expression.

Here is the link from that particular forum post in question:

viewtopic.php?f=18&t=33253&p=49871&hilit=XPath#p49871

Can you explain why is your solution better?

Thanks


Thanks for checking on the eValid forum RGarrett and welcome.

Yes, Xpath identifies a path to an element, and IF and IFE find the specific SourceIndex for the element you're looking for.

Putting REs (Regular Expresses) into the IFE command to extend it from the IF command seemed to be a natural extension...just loosening up the criteria for accepting a potential element match.

In practice, we find that IF and IFE are just simpler and easier to use than XPath.

Maybe not quite as general, but much better suited to the job of testing web applications.

For reference, here are the descriptions of both commands:

http://www.e-valid.com/Products/Documen ... ement.html

http://www.e-valid.com/Products/Documen ... nt.ex.html

And, for good measure, here is the description of Regular Expression that eValid uses (both for functional testing and for web site crawling):

http://www.e-valid.com/Products/Documen ... yntax.html

Please try them out for yourself.

Have fun!

-- eValid Support