You can specify how error conditions are handled when running
a test or schedule. Error conditions include verification point failures,
connection failures, server timeouts, custom code alerts, and problems
with data correlation.
About this task
You can specify error-handling behavior for schedules, tests, and test elements. The Errors
report displays the error conditions and error behavior that occurred in a test or
schedule.
Procedure
- In the Test Navigator, browse to a test or schedule, and
double-click it. The test opens.
- In the Test editor, complete one of the following steps:
- To specify error-handling behavior for a request or
other elements in the test hierarchy, in the Test Contents section,
select the element and in the Test Element Details section,
click the Advanced tab.
- To specify error-handling behavior for an element such
as a connection, verification point, substitution, or reference, select
the element, and then click Change. Skip to
step 5.
- To specify error-handling behavior for a datapool that
is associated with a test, on the Common Options page,
select the datapool, and then click Datapool Properties.
Click Change. Skip to step 5.
- Under Error Handling, expand Click to
show conditions. The error condition
table is displayed. The error condition table shows all possible conditions
that can be handled by the protocols in the test or schedule.
- Select the check box next to the condition for which to
specify behavior. A window opens where you can specify
the action to take and the message to log when the condition occurs.
- To apply an action when the specified condition occurs, select the Override action
upon error check box .
| Option |
Description |
|---|
| Continue |
Click to continue running the test. |
| Exit transaction |
Click to exit a transaction when the specified condition occurs. Select the
Innermost or Outermost transaction, or type the name
of a transaction. |
| Exit loop |
Click to exit a loop when the specified condition occurs. Select the
Innermost or Outermost loop, or type the name of a
loop. |
| Continue to next iteration of loop |
Click to continue to the next iteration of a loop when the specified condition occurs.
Select the Innermost or Outermost loop, or type the
name of a loop. |
| Exit test |
Click to exit the test when the specified condition occurs. |
| Exit user |
Click to stop the virtual user that encounters the specified condition. |
| Terminate run |
Click to stop the run when the specified condition occurs. |
- To contribute to the health of the page, transaction, or loop, select the Override
contribution to health status check box and select Yes. The
respective reports display the health of the page, transaction, or loop.
- Optional: To write a message to the test log when the specified condition occurs, select the
Override log message upon error check box and type a message.
- Click OK.
Example
To stop running a schedule when a substitution failure occurs
in data correlation, select the
Substitution Failure check
box. Click
Stop schedule, and then click
OK.
The
error-handling behavior that is specified closest to where an error
occurs takes precedence. If a specific request is set to continue
if a substitution fails, and the schedule is set to stop if a substitution
fails, then the schedule will continue running if the substitution
fails in that request.