During recording, StresStimulus automatically takes screenshots of the webpage on every click. Each screenshot is associated with a primary request, page or transaction issued immediately before the click. It is stored within a corresponding page object.
The screenshots are displayed when you select the request on the Test Case tree. They help users remember what was displayed in the browser when the web page was recorded. Screenshots are only available for sessions representing an HTML page. The screenshots are displayed below the page property grid. You can disable taking a screenshot by un-checking the box Take screenshot of pages as described in Recording Test Case . You can copy the screenshot to the clipboard or delete it by right-clicking the image.
|Note: StresStimulus tries to capture how the browser window looked just before the click. Sometimes when the page refreshes too quickly, or the system is a bit slow, StresStimulus can miss the right moment for a screenshot, so they may not come out well or will miss altogether.|
Some of the request properties are described in this section.
|Info: The full list of request properties, toolbar commands, and context menu options is provided in the User Interface Reference -> Test Case Tree.|
Request Timeouts - the maximum amount of time for receiving the request. Initially, the timeout of every page's request is equal to the timeout property set on the pages (see Page Timeout). You can override the request timeout on its property grid.
Caching emulation in StresStimulus is described in Test Case: Caching Rules. Every request has recorded caching behavior that is a result of the server's response headers. This information is stored in the request's Caching Rules property. You can view or change this property on the request property grid. This property only pertains to test cases with Cache-Control enabled. The Caching Rules property is summarized in the table below.
You can edit recorded sessions in the test case. To do so, in the test case tree, double-click the session (a), and in the appeared in a new Tab (b) session inspector, check “unlock for editing” (c). After that, you can make changes in the session request (d) and response (e). When finished, click Save (f)
You can skip issuing the request by disabling it.
Every request has one of two concurrency states: parallel or sequential. Requests sent in parallel are sent at the same time, while subsequent requests are sent individually. StresStimulus automatically determines a request's concurrency state using factors such as response code and Content-type. You can override the default request concurrency state by setting the Concurrency mode property to Parallel or Sequential.
Setting the concurrency mode to parallel may break parameter or cookie correlation. It is the user's responsibility to make sure that all responses that have data needed for subsequent requests be sent sequentially.
To ignore any response errors this request may encounter, set the Ignore warnings/errors to Yes. All errors will be suppressed from all error counts and Error view.
If a cookie is not automatically correlated then the recorded value will be sent during script playback. To remove not automatically correlated cookies set the Send recorded cookies? property to No.
If using components and want to hook that component to a session, then specify the component name in the component hook property.