[Webtest] RE: continue but don't abort
Wed, 17 Sep 2003 09:37:23 +0200
now I understand your point better.
The _current_ testspec is _always_ aborted on failures.
Haltonfailure only determines whether trailing _testspecs_ are to be
This is due to the concept of having one "test scenario" per testspec: if
it breaks - it's broken. Trailing steps are not executed.
WebTest is designed to be an unsupervised test executor as opposed to
a "player" that you have to visually supervise.
Your case would actually need to be broken in two testspecs.
Your >44 steps seem not to be dependend on the <=44 ones since you
expect them to run even if 44 fails. So it should be possible to do the
split. (there may be some duplication with shared steps then. - refer
to the samples on how to avoid this)
> -----Original Message-----
> From: email@example.com
> [mailto:firstname.lastname@example.org]On Behalf Of Lynn Walton
> Sent: Dienstag, 16. September 2003 0:29
> To: email@example.com
> Subject: [Webtest] RE: continue but don't abort
> >From: "Dierk Koenig" <firstname.lastname@example.org>
> >To: <email@example.com>
> >Subject: RE: [Webtest] continue but don't abort
> >Date: Fri, 12 Sep 2003 11:28:29 +0200
> >Reply-To: firstname.lastname@example.org
> >look into http://webtest.canoo.com/webtest/manual/syntax.html#2
> >start your test with following entries in the config step:
> >haltonfailure = false
> >verbose = true
> >maybe even
> >summary= false
> >if you don't need the summary file.
> >this will run your tests with appropriate messages
> >sent to stdout.
> This didn't work for me. I had also wanted some way to continue without
> I put in:
> <testSpec name="main">
> <config host="my.domain.com"
> summary="false" >
> I have a series of this same pattern but for different urls ....
> invoke, make sure the internal contents don't have a 500 error from our
> servlet engine, log (a custom step) so we can see the progress
> <invoke stepid=" get /hcm/462/ubal6-a/mod2.jsp"
> url="/hcm/462/ubal6-a/mod2.jsp" />
> <not stepid=" /hcm/462/ubal6-a/mod2.jsp contained Internal Server
> Error ">
> <verifytext stepid="500 Error" text="500 Internal Server Error"/>
> <log message=" checked /hcm/462/ubal6-a/mod2.jsp" />
> If one fails I want to see messages about the failure but still want it
> to continue.
> After adding the
> you suggested and trying ... it would still stop on the first bad link
> (404) as follows:
> output with ant using -v was like this:
> [testSpec] Completed Step: /hcm/462/ubal6-a/gradepolicy.jsp contained
> Internal Server Error " (35/88)
> [testSpec] Start Step: <unknown>" (36/88)
> [testSpec] checked /hcm/462/ubal6-a/gradepolicy.jsp
> [testSpec] Completed Step: <unknown>" (36/88)
> [testSpec] Start Step: get /hcm/462/ubal6-a/mod1.jsp" (37/88)
> [testSpec] -> gotoTarget(by url):
> [testSpec] Completed Step: get /hcm/462/ubal6-a/mod1.jsp" (37/88)
> [testSpec] Start Step: <unknown>" (38/88)
> [testSpec] Start Step: 500 Error" (38/88)
> [testSpec] Completed Step: /hcm/462/ubal6-a/mod1.jsp contained
> Internal Server Error " (38/88)
> [testSpec] Start Step: <unknown>" (39/88)
> [testSpec] checked /hcm/462/ubal6-a/mod1.jsp
> [testSpec] Completed Step: <unknown>" (39/88)
> [testSpec] Start Step: get /hcm/462/ubal6-a/m5sect7inc.jsp" (40/88)
> [testSpec] -> gotoTarget(by url):
> BUILD SUCCESSFUL
> That last line is a purposely broken link and that is where the test
> aborts but you can see it's only step 40 of 88.
> I had posted Sun Aug 24th called:
> Trying to make some custom steps that only warn rather than fail the build
> hoping to get some guidance for doing it with custom steps, but got no
> "bites". : )
> WebTest mailing list