Request step
Last updated
Last updated
Request is the main building block of tests. It represents a single API call or a user action.
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 require a body. Selecting the right content-type for your request will help us highlight the syntax of your request body (i.e. JSON or XML).
A standard GraphQL POST request should use the application/json content type, and include a JSON-encoded body of the following form:
operationName and variables are optional fields. operationName is only required if multiple operations are present in the query.
The response should return the queried data in a JSON. i.e.,
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.
The Assertions - Verify Response section allows you to validate the request response.
The Flow Control section allows to repeat the request until the parameter's value meets the requirement or number of iteration reached:
You can also set Skip and Stop conditions between requests within this section:
When we expand the request editor by clicking at the top-right of the request, we can see that a test request includes two main sections - Request and Response Handling sections.
Black input fields are fields in which you can use and .
The Headers section allows to see and set the request headers. You can add 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 .
Based on ().
The response handling section includes 3 sections: , (disabled by default), and Flow control.
To assign a static value or using the "Assign" option.
To add an extraction from . Team admins configure the repository within Settings - Suggestions.
