[Webtest] haltonfailure bug?

Dierk Koenig webtest@lists.canoo.com
Tue, 22 Oct 2002 14:24:40 +0200


This is a multi-part message in MIME format.

------=_NextPart_000_0004_01C279D6.C2271A60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

RE: [Webtest] haltonfailure bug?done (build 237)
  -----Original Message-----
  From: webtest-admin@lists.canoo.com
[mailto:webtest-admin@lists.canoo.com]On Behalf Of Dierk Koenig
  Sent: Mittwoch, 16. Oktober 2002 15:10
  To: webtest@lists.canoo.com
  Subject: RE: [Webtest] haltonfailure bug?


  I agree, the doc needs to be changed. Thanx.
    -----Original Message-----
    From: webtest-admin@lists.canoo.com
[mailto:webtest-admin@lists.canoo.com]On Behalf Of daniels@pronto.com.au
    Sent: Mittwoch, 16. Oktober 2002 4:36
    To: webtest@gate.canoo.com
    Subject: RE: [Webtest] haltonfailure bug?


    Well, this looks like an error in the documentation.

    haltonfailure: Defines that the excution of the current <testSpec> stops
if a failure of one of the test steps is detected, e.g. a <verify...> test
did not pass.

    This implies that when it is set to "false" execution of the current
<testSpec> DOES NOT STOP if a failure of one of the test steps is detected,
ie, all subsequent tests are executed.

    From the documentation, it would appear that haltonerror allows ANT to
continue, and haltonfailure allows the testspec to continue.

    > -----Original Message-----
    > From: Dierk Koenig [mailto:dierk.koenig@canoo.com]
    > Sent: Wednesday, 16 October 2002 12:41 AM
    > To: webtest@gate.canoo.com
    > Subject: RE: [Webtest] haltonfailure bug?

    Hi Dan,

    haltonfailure=false
    means to proceed with your ANT script, although your current test spec
    fails. The processing will proceed with your next test spec, not your
    next test step in the failing test spec.

    I guess you have a rather large test spec with lots of steps that get
    executed in sequence. The solution would be to break this into smaller
    test specs.

    We found that it is useful to have one test spec per "scenario", i.e.
    one path through your "use case", talking in UML terms.

    cheers
    Mittie


------=_NextPart_000_0004_01C279D6.C2271A60
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [Webtest] haltonfailure bug?</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D697591612-22102002>done=20
(build 237)</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B>=20
  webtest-admin@lists.canoo.com =
[mailto:webtest-admin@lists.canoo.com]<B>On=20
  Behalf Of </B>Dierk Koenig<BR><B>Sent:</B> Mittwoch, 16. Oktober 2002=20
  15:10<BR><B>To:</B> webtest@lists.canoo.com<BR><B>Subject:</B> RE: =
[Webtest]=20
  haltonfailure bug?<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D114360613-16102002>I=20
  agree, the doc needs to be changed. Thanx.</SPAN></FONT></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B>=20
    webtest-admin@lists.canoo.com =
[mailto:webtest-admin@lists.canoo.com]<B>On=20
    Behalf Of </B>daniels@pronto.com.au<BR><B>Sent:</B> Mittwoch, 16. =
Oktober=20
    2002 4:36<BR><B>To:</B> webtest@gate.canoo.com<BR><B>Subject:</B> =
RE:=20
    [Webtest] haltonfailure bug?<BR><BR></FONT></DIV><!-- Converted from =
text/plain format -->
    <P><FONT size=3D2>Well, this looks like an error in the =
documentation.</FONT>=20
    </P>
    <P><FONT size=3D2>haltonfailure: Defines that the excution of the =
current=20
    &lt;testSpec&gt; stops if a failure of one of the test steps is =
detected,=20
    e.g. a &lt;verify...&gt; test did not pass.</FONT></P>
    <P><FONT size=3D2>This implies that when it is set to "false" =
execution of the=20
    current &lt;testSpec&gt; DOES NOT STOP if a failure of one of the =
test steps=20
    is detected, ie, all subsequent tests are executed.</FONT></P>
    <P><FONT size=3D2>From the documentation, it would appear that =
haltonerror=20
    allows ANT to continue, and haltonfailure allows the testspec to =
continue.=20
    </FONT></P>
    <P><FONT size=3D2>&gt; -----Original Message-----</FONT> <BR><FONT =
size=3D2>&gt;=20
    From: Dierk Koenig [<A=20
    =
href=3D"mailto:dierk.koenig@canoo.com">mailto:dierk.koenig@canoo.com</A>]=
</FONT>=20
    <BR><FONT size=3D2>&gt; Sent: Wednesday, 16 October 2002 12:41 =
AM</FONT>=20
    <BR><FONT size=3D2>&gt; To: webtest@gate.canoo.com</FONT> <BR><FONT=20
    size=3D2>&gt; Subject: RE: [Webtest] haltonfailure bug?</FONT> </P>
    <P><FONT size=3D2>Hi Dan,</FONT> </P>
    <P><FONT size=3D2>haltonfailure=3Dfalse</FONT> <BR><FONT =
size=3D2>means to proceed=20
    with your ANT script, although your current test spec</FONT> =
<BR><FONT=20
    size=3D2>fails. The processing will proceed with your next test =
spec, not=20
    your</FONT> <BR><FONT size=3D2>next test step in the failing test =
spec.</FONT>=20
    </P>
    <P><FONT size=3D2>I guess you have a rather large test spec with =
lots of steps=20
    that get</FONT> <BR><FONT size=3D2>executed in sequence. The =
solution would be=20
    to break this into smaller</FONT> <BR><FONT size=3D2>test specs. =
</FONT></P>
    <P><FONT size=3D2>We found that it is useful to have one test spec =
per=20
    "scenario", i.e.</FONT> <BR><FONT size=3D2>one path through your =
"use case",=20
    talking in UML terms.</FONT> </P>
    <P><FONT size=3D2>cheers</FONT> <BR><FONT size=3D2>Mittie</FONT>=20
</P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0004_01C279D6.C2271A60--