API Monitoring Test Behaviors

API Monitoring & Testing: Test Behaviors

Each test-specific or shared environment can have separate settings for test behaviors.

Retry on Failure

When enabled, an additional test run will be triggered immediately after a failed scheduled test run. Only one new test run will be initiated per failure (failed re-runs will not re-run again). When combined with notifications set to use thresholds (e.g. notify after N failures), Retry on Failure can reduce notifications for false negatives (e.g. intermittent network issues).

Tip: You can distinguish a test re-run from a manual or scheduled test from the Source column. You can also view, when applicable, the parent test of the re-run from the Retry column.


Stop on Failure

When enabled, test runs will stop executing after the first step that fails. All subsequent steps will be skipped.

Use Cookies

When enabled, cookies will automatically be passed between requests in a test run. Cookie handling behavior is similar to a web browser, so cookies will follow typical domain, path and expiration rules. Cookie state is not persisted between test runs.

Validate SSL

Select this option to enable strict validation of SSL certificates for all HTTPS connections established when this test runs with the selected environment. If you're using a self-signed or other untrusted SSL certificate, deselect this option.

HTTP Version Support

You can determine the HTTP versions supported when executing request steps:

  • HTTP/1 only

  • HTTP/2 only

  • HTTP/2 compatibility

You can view the negotiated HTTP protocol version in the Connection tab of a test result.

Force h2c

Enable this option to force HTTP/2 over cleartext for URLS with the HTTP scheme.