This is an interesting problem that I don't understand but I have some more info to add. I was able to go to your page and verify the html, head, title, and meta tags in your page but nothing after that. So I took your source and made a local copy of it and started editing it and still couldn't get anything after your second meta to verify in XPath. Below are the verifyXPaths that work (for me at least on build 1689): <verifyXPath xpath="/html"/> <verifyXPath xpath="//html"/> <verifyXPath xpath="//head"/> <verifyXPath xpath="//title"/> <verifyXPath xpath="//meta" />
Below is what I have tried that didn't work <verifyXPath xpath="//input" /> <verifyXPath xpath="//link" /> <verifyXPath xpath="//[EMAIL PROTECTED]'http://www.gamevee.com/public/css/userprofile.css']"/> <verifyXPath xpath="//body" /> <verifyXPath xpath="//[EMAIL PROTECTED]'topnavul']"/> William Soula QA Analyst Pointserve, Inc. 110 Wild Basin Road Suite 300 Austin, Texas 78746 O: 512.617.5311 F: 512.617.0466 ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Perelstein Sent: Thursday, April 10, 2008 12:04 PM To: [EMAIL PROTECTED] Subject: Re: [Webtest] invoke/verifyxpath no elements issue Well, as a more targeted example, I can use the xpath "//div[1]/li//li[1]/a[1]" to target the element I want. This evaluates exactly how I'd expect when using webtest recorder, so I assume that my xpath is proper (syntactically at least). But this very same xpath results in a failure in webtest. I can go to the saved page linked in the webtest report and the xpath works in both xpather and the xpath tool in webtest recorder. Even the simplest of xpaths, such as "//a" or //div" fail in webtest but not in xpather or the xpath tool in webtest recorder. After putting the page through htmltidy, it was a little closer to valid, though I still got the same behavior with valid xpaths failing in webtest. Could valid xpaths failing in webtest be the result of non-compliant html?
