[Webtest] Design of com.canoo.webtest.steps.Step

[Marc Guillemot]

You're right, setting the haltonerror attribute is the solution and my
changes are unnecessary. I was irritated that an error code 500 cause
HttpUnit to throw an exception (should it really? What if we want to test
that the application sends a given error code for some requests?) and I
tryed to fix it (too) fast.

Marc.

----- Original Message -----
From: "Daniel Sheppard" <daniels@pronto.com.au>
To: <webtest@gate.canoo.com>
Sent: Thursday, May 01, 2003 4:04 AM
Subject: RE: [Webtest] Design of com.canoo.webtest.steps.Step


Is your situation:

<target name="blah">
   <testspec>
      //content
      <followframe ...> (This line fails, causing this testspec to fail)
   </testspec>

   <testspec>
      //another test
   </testspec>

</target>

And your second step is failing to run because the first step threw an
exception, which made ant bomb out and the second testspec doesn't get run?
############################################################################
#########
This email has been scanned by MailMarshal, an email content filter.
############################################################################
#########
_______________________________________________
WebTest mailing list
WebTest@lists.canoo.com
http://lists.canoo.com/mailman/listinfo/webtest