Mailingliste - Einträge 2006

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qftestJUI] Aborting Test Case On Error

  • Subject: Re: [qftestJUI] Aborting Test Case On Error
  • From: Martin Moser <martin.moser@?.de>
  • Date: Tue, 24 Oct 2006 09:01:45 +0200

Hello Tim,

you can use the try-catch mechanism of qftestJUI to structure your test-suite. So, if you put your steps into such a try-catch branch, the execution will jump into the according catch branch after an error occurred. That's the same behavior like in Java.


--On Montag, Oktober 23, 2006 10:18:25 -0400 TFrey@?.com wrote:


I've noticed that when running tests, if an error is encountered (i.e. an
expected component is not found), all of the steps after the error still
occur.  These steps almost always fail as well due to the first error.
Is there a way to have the test abort and go straight to the clean up
method once an error is encountered?  This is the way things work with
JUnit and it seems like the most reasonable thing to do.  With my current
setup, a failed test usually generates more than one error in the error
log which can be a bit confusing (and scary!).  Thanks!

Tim Frey

Martin Moser                                  Martin.Moser@?.de
Quality First Software GmbH           
Tulpenstr. 41                                Tel: +49 8171 919875
DE-82538 Geretsried                          Fax: +49 8171 919876