On the Stress Test Report page under the Session Report tab, you can review session details such as start time, duration, and execution status, in addition to other details.

Filtering

The Start/End Time filters let you specify the time interval to view only the sessions started or running during this period of time. Sessions that finished earlier than Start Time and started later than End Time will be filtered out. By default, the filters use the time of the stress beginning and end.

The Status filter allows to display only the sessions with the following status:

  • All – all test sessions.
  • Success Only – sessions with successfully executed tasks.
  • Failures Only  – sessions with errors occurred while tasks executions.

If the Only Reference Server option is selected the Reference Server sessions will be displayed in the list. 

The reference user executes a task simultaneously with LI users. Therefore, you can compare reference and LI sessions running at the same time interval in terms of duration compliance – the duration shouldn’t differ significantly. Moreover, in the case of Web Application and Web Page tasks, you can play the video of the reference session execution to track the website behavior under the stress.

To filter sessions started on the LIs, the following filters are available:

  • Zone allows filtering by geographical location the sessions were started from.
  • Agent allows filtering session list by LIs the sessions were started on.
  • User ID allows filtering by a particular virtual user ID. 

To display or edit Zone, Agent, and User ID filters (if configured), click view next to the filter field.

Viewing session details

To view session steps in detail, expand the session header.

To play the video of a reference session, filter the list by Only Reference Server, and then click the video link in the session description header.  

To view a session Performance Report, click the details link next to the session description.

Check the Errors tab of the Performance Report for failure details.

To view a description of an error in the sessions list, point to the failure status in the corresponding column. You can also find an HTTP/S task body under the Body link in the failed session description.

The most common reasons that could lead to errors in a test are the following:

  • Errors in the test configuration. In the case of a web application test, check the device configuration.
  • CPU overload on Load Injector Servers. Check CPU usage chart on the Summary tab. 
  • Client-side errors such as hardware/software infrastructure and application issues. 

See also: Error Codes