Test Case Properties
|Object type||This object type is currently selected in the Test Case tree. Its properties are displayed in this grid|
|Name||The Test Case name|
|Description||The Test Case description|
|Recorded On||The date and time when the test case was recorded|
|URLs||The number of requests in the Test Case|
|Request Size (KB)||The size of all requests in the Test Case|
|Response Size (KB)||The size of all responses in the Test Case|
|Duration (s)||The total of the response times of all pages|
|Request Timeout||Select "Enabled" to impose Timeouts specified in each request. Select "Disabled" to ignore the Timeouts. Use Disabled for determining response times of slow requests. Note: this may cause long or indefinite wait times during the test run.|
|Ignore Schema Change?||Select Yes if you do not wish to change HTTP to HTTPS protocol and vice versa for this Test Case, even if Schema Change is setup for other Test Cases|
|Think Times between pages||Specify think time to inject after every page. Select "Page-level" to use values specified in the pages (default is the recorded think time). Select "Constant" to use a constant value. Select "Random" to randomize think time. Tip: for stress tests, select "Zero".|
|Think Time (s)||A constant think time between pages.|
|Min Think Time (s)||Minimum think time|
|Max Think Time (s)||Maximum think time|
|Delay after the test case||Tips: For stress tests, select "Zero". To issue iterations with a certain frequency, select Pacing.|
|Constant delay (s)||A constant delay added after the test case replay|
|Minimum duration of the test case replay (s)||Enter the minimum test case replay duration. If the test case replays faster, the appropriate delay will be added.|
|Cache Control||Select "Enabled" to emulate browser caching and session management. Select "Disabled" to emulate browsers with disabled caching (all requests will be sent) and restarting browsers before starting a new iteration (browser sessions will not persist across test iterations).|
|New VU %||Percentage of the New vs. Returning VUs. Note: (a).On the 1-st iteration, new VUs will have an empty cache, just as a first time user. All requests will be sent. (b).On the 1-st iteration, returned VUs will have a primed cache. Caching rules for each request will be determined based on server caching headers. (c). On the subsequent iterations, all VUs are treated as returned VUs.|
|VU restarting browsers %||Percentage of VUs restarting browsers before starting new iteration. For these users, browser sessions will not persist across the test iterations.|
Select "Enabled" to impose Timeouts specified in each request. Select "Disabled" to ignore the Timeouts. Use Disabled for determining response times of slow requests. Note: this may cause long or indefinite wait times during the test run.
Ignore Schema Change?
Select Yes if you do not wish to change HTTP to HTTPS protocol and vice versa for this Test Case, even if Schema Change is setup for other Test Cases.