NeoLoad HTML results

For every build performed by TeamCity, the NeoLoad plugin makes it possible to display the NeoLoad HTML results. In TeamCity, it is necessary to select a job and a successful build before clicking NeoLoad Result to display the NeoLoad Test Report page.

  1. In TeamCity, start a build of a job configured with the NeoLoad plugin.
  2. When the test is over, click <NeoLoad job> > <successful build> > NeoLoad Result.
Results summary

This tab displays basic details of the test: project and scenario name, test duration, load policy, and so on.

Statistics summary

The statistics summary displays the following global metrics:

An icon next to each statistic indicates the severity of the statistic discrepancy with regard to the SLA profile linked to the scenario.

Hot spots

This section focuses on significant results. The times are expressed in seconds.

Top 5 errors

This section lists the five pages having produced most of the errors.

Top 5 alerts

This section lists the five longest alerts filtered by alert importance (critical alerts first, followed by warning alerts). The duration is the duration of the different occurrences of an alert as a percentage of the total test duration.

First critical alerts

This section presents the first critical alerts occurring during the test run.

Top 5 average response times

This section lists the five pages having produced the longest average response times.

Top 5 maximum response times

This section lists the five pages having produced the longest maximum response times.

Top SQL requests

The section displays the results for indicators relating to SQL requests.

Errors

This section describes the errors encountered on requests and on logical actions generating errors (Javascript actions). For every type of error, it lists the error code, the number of requests or defective logical actions, and the error description label. For more information about NeoLoad error codes (beginning with NL-), see Neotys status codes. For more information about HTTP response codes, see HTTP status codes.

Alerts

This section displays the details of the alerts triggered. The section only displays elements with at least one alert threshold set. For each element, the following statistics are displayed:

An icon is shown to indicate the state of each type of monitor with counters that have alert thresholds set:

General statistics

This section displays the following aggregated statistics for all User Paths, pages and requests:

Statistics are allocated per User Path. They are displayed in a hierarchical way. When actions are shared among User Paths, the aggregated statistics are displayed in the beginning of each section.

User Path, Transactions, push messages and pages

The following statistics are displayed for each User Path, Transaction, push message and web page:

Statistics are allocated per User Path. They are displayed in a hierarchical way. When actions are shared among User Paths, the aggregated statistics are displayed in the beginning of each section.

Media contents

For every media request, the following statistics are displayed:

The statistics are displayed per Virtual User.

Monitors

Monitors group together performance counters and indicators. The performance counters and indicators are grouped by monitored machine and by Monitor (Tomcat, MySQL, etc.). The following statistics are displayed for each performance counter:

Alert results

The alerts are grouped by monitored machine and by monitor (Tomcat, MySQL...). The following statistics are displayed for each alert:

An icon is displayed to indicate the level of each alert:

Scenario

This section shows a summary of the test scenario configuration, with the following information:

Main graphs

This section includes a collection of predefined graphs: