[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [qftestJUI] Aborting Test Case On Error
OK, I figured out what I was doing wrong. I had checked the "implicitly catch exceptions" checkbox on the wrong "level." I had it checked for each individual test case instead of the entire suite. Now everything works as it should.
Hmm, I'm wondering...
Aborting a test-case after an exception, is the default behavior in
QF-Test, so normally the question is asked the other way round, i.e.
how _not_ to abort after an error.
So the question is, are you really getting an exception like a
ComponentNotFoundException or just an error from a failed check? The
latter will indeed not abort a test unless you explicitely tell it to.
If in doubt, please send us a run-log and we'll take a closer look.
Martin Moser <martin.moser@?.de> writes:
> Hello Tim,
> you can use the try-catch mechanism of qftestJUI to structure your
> 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:
> > Hi,
> > 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
Gregor Schmid Gregor.Schmid@?.de
Quality First Software GmbH http://www.qfs.de
Tulpenstr. 41 Tel: +49 8171 919870
DE-82538 Geretsried Fax: +49 8171 919876