I took the meta tags out and tried below and it failed looking for the body
<verifyXPath xpath="/html"/>
<verifyXPath xpath="//head"/>
<verifyXPath xpath="//title"/>
<verifyXPath xpath="//body" />
William Soula
QA Analyst
Pointserve, Inc.
110 Wild Basin Road
Suite 300
Austin, Texas 78746
O: 512.617.5311
F: 512.617.0466
________________________________
From: George Policello [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 10, 2008 2:28 PM
To: [email protected]; Soula, William; [EMAIL PROTECTED]; [EMAIL
PROTECTED]
Subject: RE: [Webtest] invoke/verifyxpath no elements issue
All the checks prior to the META tag have single entries in the page. If there
are more than two META tags and the page is not well formed, is it possible
that Webtest gets stuck after the first META is found? Or it leaves the XPath
pointer at the end of the first META node so that the next queries do not go
back to the top of the document?
George
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Soula, William
Sent: Thursday, April 10, 2008 12:21 PM
To: [email protected]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [Webtest] invoke/verifyxpath no elements issue
I got a no node found error for the tests I ran against his site, that failed
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 [EMAIL PROTECTED]
Sent: Thursday, April 10, 2008 2:06 PM
To: [EMAIL PROTECTED]
Subject: Re: [Webtest] invoke/verifyxpath no elements issue
what's the error that you're getting ? Is the asserted value and test value not
matching or is something else going no behind the scenes? I tried running some
webtests on your site but was unable to connect - I thought I had the proxy set
correctly but I receive a connection refused. If I remember, I'll run the test
from home tonight. I have noticed some strange behaviors when running tests
against HTML that really up to a good standard. Would it be possible to isolate
the HTML in a new page with proper code? Just a snippet should help you out.
"Chris Perelstein" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
04/10/2008 01:03 PM
Please respond to
[EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
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?
