Setting the execution history collected during a run

The execution history is a single file that shows all events that occur during a schedule or test run. The level of history that you set determines whether you receive individual response time statistics for Percentile reports and information on verification points.

You can set the history level and also whether the history is collected from all users or from a sampling of users. Setting a sampling rate helps decrease your log size. To set the execution history and the sampling rate:
  1. In the Test Navigator, expand the project until you locate the schedule.
  2. Right-click the schedule, and then click Open.
  3. In the Schedule Contents section, click the name of the schedule and scroll down to the Execution History section.
  4. Set Execution history log level to one of the following:
    Option Description
    None Collects no execution history events.
    Schedule Collects events that correspond to actions executed in the schedule.
    Page Typically, you set history at the Page level, which collects schedule items, as well as page start and stop events. To produce a Percentile report or to see any Page Title verification points that you have set, set execution history at this level of detail or greater.
    Request Collects page information plus request-level events. To collect information about Response Code or Response Size verification points that you have set, set execution history at this level of detail or greater.
    All Collects request information plus the actual request and response data. This option produces a large history file, especially if your tests are long or you are running a large number of users. To prevent your history file from getting too large, you should set a sampling rate, rather than collecting all information from all users.
  5. To set a sampling rate, select Only sample execution history from a subset of users. The number or the percentage that you select is applied to each user group. If you are running user groups at remote locations, the number or percentage that you select is distributed evenly among the remote locations.
    Option Description
    Fixed number of users The number is applied to each user group. Assume that your schedule contains two user groups. One group contains 4 users, and one group contains 1000 users. If you sample 2 users, two users are sampled from each group.
    Percentage of users The percentage is applied to each user group—but at least one user will be sampled from each group. Assume that your schedule contains two user groups. One group contains 4 users, and one group contains 1000 users. If your sampling rate is 10%, one user is sampled from the first group, and 100 users are sampled from the second group. If your sampling rate is 25%, one user is sampled from the first group, and 250 users are sampled from the second group.
The following information is collected at the Schedule level:

The following additional information is collected Page level:

The following additional information is collected at the Request level:

The following additional information is collected at the All level:

You can export the statistics into a CSV file for further analysis. To do so, click File > Export, and select Test Execution History.

Parent topic: Representing workloads

Terms of use | Feedback
(C) Copyright IBM Corporation 2005. All Rights Reserved.