3.18.3 Reentry types

The reentry type specifies how the test should continue once the Event Handler Test Case has been executed.

Break
The test execution leaves the Test Case in which the error occurred and continues at the next Test Case or Test Step .
Continue
The test execution carries on at the next Test Case or Test Step . This is a good option when the error is relatively unimportant and does not affect the following Test Steps .
Exit
The test execution is stopped. Use this when the error is so severe that the test cannot be continued.
Return
The test execution leaves the Test Case in which the activated Event Handler is nested. This could be the current Test Case or one higher up in the hierarchy. This option is useful if you have a use case, which contains Test Cases to test a particular area or function. You can decide to leave this part of the test, and carry on at the next use case. Return will continue at the next Test Suite in a Test Job if it is activated as a default Event Handler or if there are no further steps in the current Test Suite .
Pause
The test execution is paused. To restart the test, click the pause button in the toolbar in the Jubula client .
Retry
The failed Test Step is repeated as many times as you specify in the Properties View . If the Test Step is successful on repeating, it is marked as successful after retrying. If the Test Step fails on all retries, the error type is passed on to the next parent Test Case and this Test Step (and therefore the test) is marked as failed.
See the section on best practices to learn how to use Event Handlers to document errors and ensure that the test continues running 5.4.



Copyright BREDEX GmbH 2011. Made available under the Eclipse Public License v1.0.