Extraction & Assertion step
Last updated
Last updated
The extraction & assertion step allows extracting, assigning parameters and add validations without spinning an entire request. Among it's usages are assigning or allocating values at the beginning of a flow of after calling a generic shared flow and we need to extract/re-assign/validate additional flow specific data.
The Extract & Assert step consists of three main areas:
Extraction section - a place to assign and extract the parameters. Note that the extractions will refer to the last response that was introduced, ie. the previous response.
Each extraction consists of three parts:
Parameter name - the name that the parameter will be referenced when used, this filed can accept letters, numbers and undescores (`_`).
Assignment method/type - A selection of methods that can be used to acquire the value for the parameter. The available methods are: Assign, JSONPath, Clojure, xPath, RegExp, Header and WebSocket. For detailed explanation about each one of the methods please refer to the Extractions documentation.
Assertions area - A place for data validations (Assertions)
The assertions section consists of three areas:
The parameter that carries the value for the validation.
The comparison method (the operator), also referred as the value, the available operators are Exists, Doesn't exists, Equals, Doesn't equals, Contains, Doesn't contains, Matches, Greater than, Less than, JSON Schema, JSON Contains, XML Contains. For detailed explanation about each one of the comparison methods please refer to the Assertions documentation.
The expression - when applicable, this value will carry the compared value or expression for the validation.
Flow control area - Allows skipping to another step, stopping the flow and add wait time after step execution.