Hi, to see what WebTest "sees", you can print the current state of the DOM to the console with something like: <groovy> println step.context.currentResponse.asXml() </groovy>
which shows that the whole page content is placed within <title>...</title>. This is a bug occurring with NekoHTML 1.9.6.2 when the </title> is missing. I've released a version 1.9.7 of NekoHTML last week which (among others) fixes this problem. You can safely replace version 1.9.6.2 with version 1.9.7 until I've put it into WebTest. Cheers, Marc. -- Blog: http://mguillem.wordpress.com Chris Perelstein wrote: > I'm a fairly new to webtest, so I may be missing something horribly > obvious here, but I'm having an issue with not being able to use > verifyxpath on any elements when I load a specific page. As I backed > off on the depth of what I was trying to identify, I discovered I > couldn't even match the body of the document. The html is horribly > invalid, and my current theory is that this is the source of my problem, > but I'm not entirely sure. Most pages on the site haven't given me too > much trouble. The simplified version of the test is as follows: > > <invoke url="http://www.gamevee.com/user/perelstein/videos"; /> > <verifyXPath xpath="//a" /> (FAILS) > <verifyXPath xpath="//body" /> (FAILS) > <verifyXPath xpath="/html" /> (FAILS) > > Any insight is highly appreciated. _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
