The Request operation corresponds to individual HTTP requests in your scenario.
Depending on the request method (GET, POST and so on) and on the type of the content that the tested web server returns for a request, LoadComplete recognizes the following request types:
|POST||Sends data to a server.|
|GET||Retrieves the specified resource from the server. Depending on the type of the content that the server returns, the following request types can be distinguished:
|HEAD||Retrieves the headers that the server would return if the specified resource were requested by the GET method.|
|COPY||Creates a copy of the specified resource on the server.|
|MOVE||Moves the specified resource on the server.|
|PUT||Creates or replaces the specified resource on the server.|
|PATCH||Updates the specified resource on the server.|
|TRACE||The tested server echoes the request content back.|
|CONNECT||Establishes a tunnel to the specified resource.|
|OPTIONS||Retrieves information on the communication options available for the specified resource.|
|DELETE||Deletes the specified resource from the server.|
Secured requests are marked with the glyph.
|Number of occurrences:||Unlimited.|
|Parent operations:||Connection, Page (if connections are hidden in the scenario editor), Scenario (if pages and connections are hidden), Group, If, Loop, While.|
|Child operations:||The operation cannot have child operations.|
The Think Time edit box at the top of the editor specifies the number of milliseconds LoadComplete will wait before simulating the request.
The SLA edit box at the top of the editor specifies the maximum acceptable time to fist byte of the request, in milliseconds.
On this page you can view and change the contents of the simulated request. The page contains the following panels:
|Request Header||Displays standard and custom headers of the request.|
|Request Body||Displays the request body contents. Available for POST and PUT requests.|
|Data Replacers||Shows rules for replacing request contents and cookies with variables. You use this feature to insert needed data to your requests. For instance, to implement data-driven tests, you may replace recorded data with data loaded from a CSV file or Excel sheet.|
|Uses Data From||A list of variables that are used in the request headers and body. If a variable extracts data from some other request, the panel displays this variable as a child item of that request.|
On this page you can view and change the contents of the expected response, and save response data to variables. The page contains the following panels:
|Response Header||Displays the response header data.|
|Expected Codes||Specifies what response codes LoadComplete will treat as success, error or warning.|
|Response Body||Displays the response body contents (if any). You can also change response body data on this page (that is, you change the data that LoadComplete will expect to receive from the server in the response).|
|Data Selectors||A list of data selector rules (LoadComplete uses them to extract data from responses and save them to variables).|
|Provides Data For||Displays a list of requests that use variables, whose data you specify on the Data Selectors page.|
|Validators||A list of rules for checking the response contents.|
This page provides summary information on the operation like the number of found errors, the list of variables used, and so on. Information on the page is read-only.
You can find information on issues in operation properties in the Summary page. Also, information about the erroneous settings is displayed in the editor’s header area.
|For information on …||See the following topics …|
Extracting data from responses and inserting it into subsequent requests
Using variables to specify parameter values
Working in the Scenario Editor