During test execution, StresStimulus records HTTP session information into the test log, which is stored in the test repository along with Metadata. The Metadata includes information, such as VU number, iteration number, and test case name, which help to find session information quickly. To display necessary replayed sessions in the session grid:

1. Click Show Sessions located in the Test Result tab toolbar.

2. A query builder window pops up.

3. Each search criteria, such as VUs, Iterations, Sessions, Test Case, and Agent names, has its own designated text box.

a. Multiple numeric values or ranges can be combined in each text box. For examples: for VUs, Iterations, and Sessions use format 1-3, 5, 9;

b. A comma should separate multiple names. For example, for Test Cases and Agents, use format Name1, Name2

Tip: Leave textboxes empty to broaden the search.

4. For responses with Successes, Errors, and/or Timeouts: check 1 or 2 or 3 boxes. Checking all or un-checking all will render all sessions.

5. You can select sessions sent within a specific time range, received within a specific time range or combination of thereof.

      • Check the Filter by Time Range box
      • Select Send, Received or both
      • Enter the time range into the From / To boxes in seconds from the beginning of the test

Tip: The easiest way to enter retrieve sessions sent or received during certain time intervals it to query the test log from the graphs ( see Retrieving Sessions from Graphs).

6. Click Show Sessions button

7. Requested sessions will be displayed in the session grid.



  • Retrieving more than 1,000 records, as entered in the Max Sessions box, can impact performance.
  • Querying Test Log requires that session content to be saved in the storage accessible from the controller. This information is available in tests that ran from the controller without agents. In  Distributed Testing howeverthis information is available only when SQL Server is used as Test Result Storage . In distributed tests with SQL Server CE-based storagesome of the session content is stored locally on the agents and is not accessible from the controller. Therefore, only VUs emulated on the controller can be queried.

  • No labels