Performance Test Report

Events are soft errors or warnings that don't interrupt the flow of testing. Request-level errors also log an event because it depends on the test configuration if they turn into a hard failure as well.

You can use the XLT API and create your own events to learn about certain conditions, such as an unavailable product that doesn't cause the test to stop but that needs your attention. A few out-of-stock products may be okay while too many of them could affect the test behavior.

The Overview section below lists all events and their respective count in general. The Details section beneath lists and counts all events grouped by test case name, event name, and the particular event message (URLs, for example).

In case of too many events, the XLT report will limit the number of collected data points and report dropped counts instead. You can use the reportgenerator.properties to control these limits. If the report displays "XLT::Dropped events due to bad naming", you might have used the name of an event to communicate dynamic data and XLT limited the data collection to avoid memory problems. You can raise the limit, in case you have a higher number of legit event names.