Request is the most basic building block of tests. It represents a single API call or a user action.
When we expand the request editor by clicking the ADVANCED button, we can see that a test request includes two sections - The request main section (In yellow) and the response handling section (In blue).
The Method and URL fields are the most basic requirements for a valid request.
It is recommended to set the Request description in a way that describes its action. This will make it easier for you to debug your tests later if this request fails.
Some requests requires a body. Selecting the right content-type for your request body will help us highlight the syntax of your request body (i.e. JSON or XML).
The Headers card allows to see and set the request headers. You can add a header to all requests or as a Global Header so that it will be added to all of the test flow requests and appear in the Global Login tab.
The response handling section includes 3 cards: Extractions - Set Parameters, Assertions - Verify Response and Loops. It allows you to extract values from the request's response and validate them.
To extract values from the response body into an existing or a new parameter using JSONPath, Closure, jQuery, RegExp.
To extract an HTTP header value into a parameter using the Header extractor.
To assign a static value or apply a function on another parameter using the "Assign" option.
To add an extraction from the Suggestions repository. Team admins configure the repository within Settings - Suggestions.
The Assertions - Verify Response card allows you to validate the request response, find more information here.
The Loops card allows to repeat the request until the parameter's value will meet the requirement or number of iteration reached: