During recording, StresStimulus automatically takes screenshots of the webpage on every clickEach 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 screenshot by un-checking the box Take screenshot of pages as described in Recording Test Case. You can copy the screenshot to clipboard or delete it by right-clicking the image.

    Icon
    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. 

    Icon
    Info: The full list of request properties, toolbar commands and context menu options is provided in the User Interface Reference -> Test Case Tree.

    Timeout

    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 Timeout). You can override the request timeout on its property grid.

     

    Icon

    Info: Because responses for the timed out sessions are not received in time, they cannot be stored in the test log. Session inspector will display the message "StresStimulus timeout" in place of the response content when you open a session with a timeout.  

    Caching Rules

    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.

     

    Caching RulesProperties
    NormalAll recorded caching headers will be sent. A possible 304 Response can come if the resource has not changed.
    Not CachedAll recorded caching headers are stripped off and the request is sent. Expect a 200 response.
    CachedThis request will not be sent because it is cached.

     

     

    Icon

    Note: If the URL of a request is parameterized, then caching for such requests is automatically disabled regardless of user settings. This helps to avoid the mistake of caching requests with dynamic URLs.


    Editing Sessions

    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)


     

    Disabling

    You can skip issuing the request by disabling it. 

     

    Concurrency mode

    Every requests has one of two concurrency states: parallel or sequential. Requests sent in parallel are sent at the same time while sequential requests are send 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.

    Note

    Icon

    Setting the concurrency mode property does not guarantee concurrency state. A request is a parallel concurrency mode can still be sent sequentially if it's response is critical for subsequent requests.

     

    • No labels