Clients
This module contains step implementations for the Clients tasks.
Then client get endpoint payload metadata
Then get "{endpoint}" with name "{name}" and save response payload in "{payload_variable}" and metadata in "{metadata_variable}"
Create an instance of a Clients task, actual implementation of the task is determined
based on the URL scheme specified in endpoint
.
Get information from another host or endpoint than the scenario is load testing and saves the response in a variable.
See Clients task documentation for more information about client tasks.
Example:
Then get "https://www.example.org/example.json" with name "example-1" and save response payload in "example_openapi" and metadata in "example_metadata"
Then get "http://{{ endpoint }}" with name "example-2" and save response payload in "endpoint_result" and metadata in "result_metadata"
Arguments:
endpoint
str - information about where to get information, see the specific getter task implementations for more informationname
str - name of the request, used in request statisticspayload_variable
str - name of, initialized, variable where response payload will be saved inmetadata_variable
str - name of, initialized, variable where response metadata will be saved in
Then client get endpoint payload
Then get "{endpoint}" with name "{name}" and save response payload in "{variable}"
Create an instance of a Clients task, actual implementation of the task is determined
based on the URL scheme specified in endpoint
.
Get information from another host or endpoint than the scenario is load testing and saves the response in a variable.
See Clients task documentation for more information about client tasks.
Example:
Then get "https://www.example.org/example.json" with name "example-1" and save response payload in "example_openapi"
Then get "http://{{ endpoint }}" with name "example-2" and save response payload in "endpoint_result"
Arguments:
endpoint
str - information about where to get information, see the specific getter task implementations for more informationname
str - name of the request, used in request statisticsvariable
str - name of, initialized, variable where response payload will be saved in
Then client put endpoint file destination
Then put "{source}" to "{endpoint}" with name "{name}" as "{destination}"
Create an instance of a Clients task, actual implementation of the task is
determined based on the URL scheme specified in endpoint
.
Put information, source being a file, to another host or endpoint than the scenario is load testing and saves the response in a variable
See Clients task documentation for more information about client tasks.
Example:
Then put "test-file.json" to "bs://my-storage/my-container?AccountKey=aaaabbb=" with name "upload-file" as "uploaded-test-file.json"
Arguments:
source
str - relative path to file infeature/requests
, supports Templatingendpoint
str - information about where to get information, see the specific getter task implementations for more informationname
str - name of the request, used in request statisticsdestination
str - name of source on the destination
Then client put endpoint file
Then put "{source}" to "{endpoint}" with name "{name}"
Create an instance of a Clients task, actual implementation of the task is determined
based on the URL scheme specified in endpoint
.
Put information, source being a file, to another host or endpoint than the scenario is load testing and saves the response in a variable
See Clients task documentation for more information about client tasks.
Example:
Then put "test-file.json" to "bs://my-storage?AccountKey=aaaabbb=&Container=my-container" with name "upload-file"
Arguments:
source
str - relative path to file infeature/requests
, supports Templatingendpoint
str - information about where to get information, see the specific getter task implementations for more informationname
str - name of the request, used in request statistics