Hi Stefan,
Can you run the following two targets and let us know what results you get?
I just ran them with the latest build and they appear to produce the documented
behaviour (i.e. error2 and failure2 cause a halt but not the earlier steps).
Thanks, Paul.
-----------
<target name="errorcases">
<webtest name="error0">
<config haltonerror="false" errorproperty="the.error"/>
<steps>
<not description="not doesn't invert a StepExecutionException">
<invoke url="http://dummy0.http"/>
</not>
</steps>
</webtest>
<echo message="${the.error}"/>
<webtest name="error1">
<config haltonerror="false" errorproperty="the.error"/>
<steps>
<invoke url="http://dummy1.http"/>
</steps>
</webtest>
<echo message="${the.error}"/>
<webtest name="error2">
<config haltonerror="true"/>
<steps>
<invoke url="http://dummy2.http"/>
</steps>
</webtest>
</target>
<target name="failurecases">
<webtest name="failure0">
<config haltonfailure="true" errorproperty="the.failure"/>
<steps>
<not>
<verifyProperty name="xyzzy0" text="xx"/>
</not>
</steps>
</webtest>
<echo message="${the.failure}"/>
<webtest name="failure1">
<config haltonfailure="false" failureproperty="the.failure"/>
<steps>
<verifyProperty name="xyzzy1" text="yy"/>
</steps>
</webtest>
<echo message="${the.failure}"/>
<webtest name="failure2">
<config haltonfailure="true"/>
<steps>
<verifyProperty name="xyzzy2" text="zz"/>
</steps>
</webtest>
</target>
Stefan Voß wrote:
Marc Guillemot schrieb:
Stefan Voß <[EMAIL PROTECTED]> writes:
Hallo,
I updated from build 1000 to 1212 yesterday and I'm facing the
following problem:
Webtest seems to ignore the value of the haltonerror and
haltonfailure property from the config part and always halts on
failures and errors. I've edited the webtestrunner.xml so it now
contains the import of the taskdef.xml and my resultfile "result.xml"
contains the two properties with the values I've set. Any suggestions?
how does your test look like? It's quite surprising because webtest
selftests test these features too and
haven't complaint about behavior changes.
Marc.
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
The test is quite simple. It only clicks through the application and
checks if there are any ServletExceptions. The failing part of the test is:
...
<clickButton
htmlId="${data.search.buttonName}"
description="Suche Button klicken."/>
<not>
<verifytext
text="${data.error.1}"
description="Es sollte keine Exception auf der Seite
aufgetreten sein."/>
</not>
The data.error.1 is set:
data.error.1=xception
The Page includes a ServletException so the not-step fails causing the
testsuite to halt.
...
The config part looks like this:
<config
protocol="${application.protocol}"
host="${application.host}"
port="${application.port}"
basepath="${application.basepath}"
haltonfailure="false"
haltonerror="false"
summary="${webtest.createSummary}"
saveresponse="${webtest.saveResponse}"
failureproperty="test.failure"
errorproperty="test.error"
resultpath="${webtest.config.resultpath}"
resultfile="${webtest.config.resultfile.name}"
>
<header name="Accept-Language" value="de-de"/>
</config>
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
