Hi guys, 

I have several pages bombing out early due to what seems to be a rather groce 
parsing error in a verifyXPath step for the /html/head/title. 

The error messages look like following excerpt:
--------------------------------------------------------------------------
BUILD FAILED
D:\tools\webtest-2.6\webtest.xml:184: The following error occurred while executi
ng this line:
D:\workspaceJP\jp-ep2i-tests-Canoo\src\main\web-test\usecases\allTests.xml:132:
The following error occurred while executing this line:
D:\workspaceJP\jp-ep2i-tests-Canoo\src\main\web-test\usecases\allTests.xml:141:
The following error occurred while executing this line:
D:\workspaceJP\jp-ep2i-tests-Canoo\src\main\web-test\usecases\login\loginDeAgeLo

wer18.xml:13: Wrong result for xpath >/html/head/title<. Expected value "Profil
administratif/signalΘtique - Conditions α l'inscription non remplies" but got "P
rofil administratif/signalΘtique - Conditions α l'inscription non remplies</titl
e> <meta http-equiv="Cache-Control" content="no-store" /> <meta http-equiv="Prag
ma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> <meta http-e
quiv="Content-Type" content="text/html; charset=ISO-8859-15" /> <link rel="style
sheet" href="/jp-ep2i/styles/styleFxxxx.css" type="text/css" media="screen"/> <s
cript language="JavaScript" type="text/javascript"> // Cette fonction permet de
vΘrifier la validitΘ d'une date au format jj/mm/aaaa function isDate(d) { // Si
la variable est vide on retourne faux. if (d == "") return true; // On teste l'e

... rest of the page here ...

 </body> </html>"

Total time: 4 seconds
--------------------------------------------------------------------------

It looks as if wt has his document tree mixed up and considers everything 
following the title's start tag as being part of the title. All pages 
presenting this behaviour do validate using the FF HTML Validator extension.

Upgrading to latest build does solve the problem but breaks numerous 
verifyXPath's that do work in wt 2.6. So it seems I'm stuck in a dead end 
street...

Any ideas on how to avoid the 'parse error' or the xpath issue of the latest 
build R_1716? 

TIA, Avander








_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest

Reply via email to