/
1. Assertions - HTTP Response Verification & Actions on Failure

1. Assertions - HTTP Response Verification & Actions on Failure

Introduction to Response Verification

Avoid executing tests without controlling the received content of URL calls by comparing them to the originally recorded data.

Many errors from Web server applications are embedded inside valid HTTP 200 responses. Therefore, the content of the responses must be also be checked to detect content errors under load.

For this reason, ZebraTester examines the content of all recorded URL calls and automatically applies a content check per each URL call using a heuristic algorithm. This algorithm performs content checks by searching for an ASCII-text string inside the received content; however, if this seems impossible, or if this doesn't seem to make sense, the received content is checked by its size (content length) instead of by searching an ASCII-text string.

So you can use one (or more) variables from the Var Handler as part of a test-string on the URL using the Response Verification view.

Icon/View

Screenshot

Icon/View

Screenshot

Default View: Waterfall

There will be two alternate views of the recorded data; the default is a waterfall view of the URL Calls, with the specific recorded information for each row.

 

The other is the Alternate Response Verification View that will test the responses against the parameters you set.

An eye icon-toggle, found in the upper right, indicates if you are in the waterfall view (grey eye) or the response Verification View (green eye). If you are in the waterfall view (Above), click the grey eye icon to access the “Alter View,” which is short for the Alternate