Mailing list - Entries of 2006

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

[qftestJUI] Manual 14.8.2 Test: Implicitly catch exceptions

  • Subject: [qftestJUI] Manual 14.8.2 Test: Implicitly catch exceptions
  • From: "Eton Cohen" <ec@?.com>
  • Date: Tue, 6 Jun 2006 11:36:50 -0400

To All:


Recently, I have been having trouble using the “Implicitly catch exceptions” attribute of “Test”. Below is the definition for this attribute in the Manual (14.8.2 Test: Implicitly catch exceptions):


Implicitly catch exceptions

If the Setup and Cleanup of the test are set up so you can guarantee the same initial conditions for each child node even in the case of an exception, you can set this attribute to make the Test catch the exception implicitly. That way, if an exception is caught from a normal child node, the exception is logged and the execution of that child node is stopped. Then the Test continues with the Cleanup as if nothing had happened.

Recently, I am finding that even though Implicitly catch exceptions” is checked, the test suite gets stuck on an exception and does not continue. I used to not have any problem as long as I had the "Implicitly catch exceptions" checkbox checked. The test suite would continue until the end. Now, when the first exception occurs, it stops at that point.

In case it makes a difference, the structure of my tests is as follows:

-          Test-suite

-  Test

   +  Setup

   +  Test

   +  Test

   +  Test


   +  Cleanup

I have the “Implicitly catch exceptions” checked in both the 1st level Test (under the Test-suite) as well as in the 2nd level Tests (in between the Setup and Cleanup).

Any ideas on how to solve this problem would be appreciated.



Eton Cohen