Hi Chris,
well, your page would profit from cleaning the html a little ;-)
Anyway, try this:
//[EMAIL PROTECTED]'clanvideolist']/div[1]//[EMAIL
PROTECTED]'clanvideo']/[EMAIL PROTECTED]'videotext
']//a
i.e.
from the unordered video list
take the first div below (that indicates the 'row' in your design)
find the ul for the video
with li videotext (to filter away other anchor elements)
and finally locate the nested anchor
happy testing
Dierk
| -----Original Message-----
| From: [EMAIL PROTECTED]
| [mailto:[EMAIL PROTECTED] On Behalf Of Chris Perelstein
| Sent: Donnerstag, 10. April 2008 19:04
| 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?
|
|
