Specify error-handling behavior

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.

You can specify error-handling behavior for schedules, tests, and test elements.

1. In the Test Navigator, browse to a test or schedule, and double-click it.

2. Under Test Element Details or Schedule Element Details, click the Advanced tab.

   1. To specify error-handling behavior for a request, select the request before clicking the Advanced tab.

   2. 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.

   3. To specify error-handling behavior for a datapool associated with a test, on the Common Options page, select the datapool, and then click Datapool Properties. Click Change. Skip to step 5.

3. 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.

4. 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.

5. Select the action to take when the specified condition occurs.

   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 set the name of a transaction.
   Exit loop	Click to exit a loop when the specified condition occurs. Select the Innermost or Outermost loop, or set 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 set 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.
   Stop schedule	Click to stop the schedule when the specified condition occurs.

6. Optional: Type a message to be written to the test log when the specified condition occurs.

7. 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 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.

Related:

Redirection support for HTTP tests
HTTP test editor overview
Cut and paste in tests
Specify the number of allowable URL redirects during test runs
Define performance requirements in tests
Add an authentication folder
Verify expected behavior
How loops affect the state of virtual users
Split a test
Split a test page
Merge test pages
Disable and enable secondary HTTP requests
Reuse tests on different hosts: Server connection variables
Convert tests to use SSL connections
View a test in the Protocol Data view
Test Siebel applications

Related reference:

Error conditions

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.