Hi Linda,
Looking at your example from earlier, I don't see two webtests Here is what
you originally setnt
<project default="test">
<target name="test">
<webtest name="my simple Test">
&goToSite;
<clickLink label="Home"/>
<verifyText
text = "Our primary goal is xto provide"
description = "Display of middle of paragraph"
/>
<clickLink label="Services"/>
<verifyText
text = "Webpage design and development"
description = "Check text on Services page"
/>
</webtest>
</target>
</project>
Try the following instead:
<project default="test">
<target name="test">
<webtest name="my simple Test">
&goToSite;
<clickLink label="Home"/>
<verifyText
text = "Our primary goal is xto provide"
description = "Display of middle of paragraph"
/>
</webtest>
<webtest name="my simple Test">
&goToSite;
<clickLink label="Services"/>
<verifyText
text = "Webpage design and development"
description = "Check text on Services page"
/>
</webtest>
</target>
</project>
Once a step within a <webtest> tag fails, none of the other steps are
processed. You can define multiple <webtest> tags within a project.
Cheers,
John Spann | Associate Software Engineer
Citrix Online Division
Citrix Systems, Inc.
6500 Hollister Avenue
Goleta, CA 93117 USA
www.citrix.com
Phone: 805.690.3489
Cell: 805.729.0008
Email: [email protected]
________________________________
From: Linda de Boer <[email protected]>
Reply-To: <[email protected]>, Linda de Boer <[email protected]>
Date: Thu, 23 Apr 2009 18:24:03 -0700
To: <[email protected]>
Subject: [Webtest] RE: Continuing tests after a step failure
G'day
I found that using the "haltonfailure" config option, that I still could
not get the test to continue to the next step.
According to the documentation "Even when set to "false" all of the
trailing <step>s of the current <webtest> will be skipped but processing
will continue with the next <webtest>.". If I understand this and all
the other threads I've read today, I need to start a new "<webtest>" for
the next test step. If this is so, then I need a new invoke. This has
also been noted by another fellow in one of the threads, but I can't
find it again.
I am thinking that I have misunderstood something because this is a very
well organized package. I figure I've got to have missed something. Is
there a way around this that I have not found?
What I am currently doing is just testing menu buttons and verifying
pages. A simple starter. But I'd like a full report of all the buttons,
pass or fail, all at once. Not one or two at a time depending upon when
it failed. Am I trying to do something that I should not?
Thanks much......;-)
--
ldb
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
