Executing HTTP/1 requests and receiving responses from the server. It can work with HTTPS traffic.
Assigns the appropriate HTTP request method.
Adding a parameter to a request's query.
Instead of multiple calls to this method, it is possible to make one call by passing an object with multiple query part as a parameter:
Adding a header to a request.
Instead of multiple calls to this method, it is possible to make one call by passing an object with multiple headers as a parameter:
Adding a cookie to a request.
Instead of multiple calls to this method, it is possible to make one call by passing an object with multiple cookies as a parameter:
Adding a data to a request's body.
The result of executing the request is placed in a special "response" object.
This object contains several methods and properties for getting data:
This property returns the response code from the server.
This property returns the status string of the response. For example "HTTP/1.1 200 OK"
This method returns the header by name. In case of multiple headers with the same name, the first one is returned.
This method returns the cookie by name
This property returns the body object of the response which contains several properties for getting data:
This property returns the size of the body data in bytes.
This property returns the raw text of the response. By default, UTF-8 encoding is used.
This property returns the js object received from the json response. If the json is invalid, an exception will be thrown.
свойство возвращает значение по хпаф выражению из json или xmlThis property returns the raw body data as array of bytes.
This property returns the value by regexp expression.
This property returns the value by xPath expression from json or xml. If the json or xml is invalid, an exception will be thrown.
Sets the authorization type and required credentials to perform automatic authorization.
This method exists in two variants:
Executing HTTP/2 requests and receiving responses from the server. It can work only with HTTPS traffic.
Coming soon...
Sending and receive WebSocket messages to and from the server. It can work with HTTPS traffic.
Sending a text message without waiting for a response.
Sending a message with an array of bytes without waiting for a response.
Waiting for and receiving an incoming text message.
Waiting for and receiving an incoming byte array message.
Executing API call using a Swagger definition.
Print a loaded definition to console
Checking values outside the request chains. In case of a failed check, a message is posted to the blog.
Checking the result of the expression for truth.
Checking the equality of the actual and expected values.
An object for optional actions with the project execution log.
Adding an informational message without changing the final status of the test.
Adding a warning to the project execution log. If the current final status is better than "Warning", then it changes to "Warning".
Adding a error to the project execution log. If the current final status is better than "Error", then it changes to "Error".
To simulate pauses between the actions of a real user or client application, the pause operation is used.
The delay duration of this operation is equal to a random value in the range between the two parameters of this operation.