Assert Suite

This section will provide you with the current execution results so you can add custom assertions to your scenario, there are several assertion types available from the assert type drop-down menu, some assertions are exclusively for requests. For most assertions, AIQ UI will provide you with current results information so you don’t have to find out the current results to validate against. These are the available assertions:

• Assert Exists: Validates whether or not the target element exists in the results tree.

• Assert Size: Validates the actual size of the desired target against the given custom value. Comparison criteria can be set to: equals, not equals, less than, more than, less or equal, more or equal.

• Assert Duration: Validates the actual duration of the desired target against the given custom value. Comparison criteria can be set to: equals, not equals, less than, more than, less or equal, more or equal.

• Assert Matches (Request only): Compares a request-response content to validate if the given baseline string is contained in the request-response delimited by the given target accessor. The user must know and specify the request-response content format, target accessor field changes according to the response format, if the response format is plain text, use regular expressions to limit the response range to valid (using “.*” will validate against the whole response), if the response format is JSON then provide the JSON path to the desired element to assert, if is XML provide the XPath to the desired tag, the only available formats that AIQ can handle so far for this procedures are: text, JSON and XML.

• Assert Checksum (Request only): Validates the actual request-response checksum against the given custom checksum.

• Assert Response Code (Request only): Validates the actual request response code against the given custom response code.

• Store Content: The very first thing to know about this is that is NOT an assertion, this is an auxiliary function of AIQ which provides the user the ability to store request-response content into an internal custom-named variable in The Locker, which can be used on a further request if required. For example, imagine you have a shopping cart web application, one of your requests generates a unique ID number associated with each cart, let’s assume that this number is required to process transactions, under this context, you could store the first request response (the ID) and then instruct AIQ to use it at the expected request taking the value from the stored content.