The Scenario node is a top-level element in the scenario hierarchy. You can neither delete, nor add or edit it in scenarios.
|Number of occurrences:||Only once. The topmost item in the operation tree.|
|Child operations:||Any other operation.|
The Think Time edit box at the top of the editor specifies the number of milliseconds to wait before the scenario starts running.
The SLA edit box at the top of the editor specifies the maximum acceptable duration of the operation, in milliseconds. For the Scenario operation, it corresponds to the time it takes to execute a scenario completely.
This page provides summary information on the operation and its child operations like the number of found errors, the list of variables used, and so on. Information on the page is read-only.
To determine whether a request was simulated successfully, LoadComplete compares the response code received from the server during the test run against the expected response code the response specifies. If the response code differs, LoadComplete will post a warning to the test log.
If a scenario calls other subscenarios, then its expected response codes are ignored. Use a subscenario's expected response codes instead.
On the Expected Codes page of the Scenario operation, you can configure how LoadComplete will treat this or that response code: Warning, Error or OK (success).
Unlike the expected codes you set for an individual response, expected codes you set on this page will be applied to the whole scenario.
To learn how to set expected codes, see Setting Expected Response Codes.
HTTP specification (RFC 2616): http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
WebSocket specification (RFC 6455): https://tools.ietf.org/html/rfc6455
On the Data Replacers page, you can define rules for replacing request contents and cookies with variables. You can use this to implement data-driven tests by replacing recorded data with data loaded from external files.
Unlike data replacers you set for individual requests and client messages, data replacers you set on this page will be applied to the entire scenario.
To learn how to create data replacers, see Creating Data Replacers.
If a scenario calls subscenarios, its global data replacers will be ignored in the subscenarios. Specify data selectors for each subscenario individually.
If it applies a data replacer that modifies the request body content (with the Body (RegExp) area) to a
GET request, the resulting request may have a non-empty payload. HTTP/1.1 specification does not recommend using
GET requests with a non-empty payload body (to learn more, see Section 4.3.1 of RFC 7231). Your tested web server may reject such a request, or return an unexpected response.
To avoid possible issues, make sure that the regular expression of your scenario-level data replacer matches data only in the needed requests. As an alternative, instead of using scenario-level data replacers, create individual data replacers only for requests whose data you want to modify.
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.