Hi Marc,
thank you for your reply.
a little backgrond to my (very simple) testcase:
unfortunately the testwebsite is cut in three ore more application areas
(menue,header,text,footer,...).
the content is provided for example in the menue-, in the header- and in the
text-area.
the testcase should give the guarrantee, that the content stands in the
text-area.
if i use the command <verifyText>: WebTest would give me an OK (because it
will be find in the menue-area),
but that is'n the guarrantee, that the content is in the text-area.
that's why i use the command <verifyXPath>.
if you have an other/better idea (to veryfy a text in th text-area or at an
defined postion) please tell me.
i'll upload the site (with some content changes).
greetings,
http://www.nabble.com/file/p21869813/site.html site.html Martin
Marc Guillemot wrote:
>
> Hi Martin,
>
> do you seriously use such an XPath expression? Except in very very
> special cases, ugly absolute XPath expressions don't make sense and are
> a very bad idea. In fact I think that WebTest should refuse them (as
> well as this mailing list) to force user to use better XPath
> expressions! ;-)
>
> Can you provide the html page?
>
> Cheers,
> Marc.
> --
> Web: http://www.efficient-webtesting.com
> Blog: http://mguillem.wordpress.com
>
> Martin_HH wrote:
>> hi @ll,
>>
>> in december I have start with webtest(1729) and create 10 Tests with ~300
>> Steps.
>> And everything was OK.
>> Only the easy one like clickLink, verifyText and verifyXPath.
>> One of them:
>> <verifyXPath description="Instrumentsuche"
>> xpath="/html/body/div[2]/div[2]/div[2]/div[1]/div[1]/ul/li/a"
>> text="[\s(Instrument Suche)\s]" regex="true"/>
>>
>> Now I have changed to webtest(1738) and if I now run the old tests I get
>> an
>> Error:
>> Message
>> Wrong result for xpath
>>> /html/body/div[2]/div[2]/div[2]/div[1]/div[1]/ul/li/a<
>> Details
>> expected value [\s(Instrument Suche)\s]
>> actual value
>>
>> There are no changes on the website or in the tests.
>> If I put the xpath in the FF3 extension "XPath Checker" or "XPather" both
>> give me the expected value.
>>
>> Why dosn't the "new" WebTest get the old an right value.
>> Is there a bug in the new version or a mistake in my test?
>>
>> thanks
>> Martin
>>
>
>
> _______________________________________________
> WebTest mailing list
> [email protected]
> http://lists.canoo.com/mailman/listinfo/webtest
>
>
--
View this message in context:
http://www.nabble.com/WebTest-%281738%29-don%27t-like-xpath--tp21730384p21869813.html
Sent from the WebTest mailing list archive at Nabble.com.
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
