Statistics Tab

Last modified on September 06, 2021

The Statistics tab of the test results screen displays metrics on timings and types of failures happened during the test run. To get information on separate test steps (URLs or synthetic steps in UI tests; requests in API tests), click the test in the list.

Statistics tab

Click the image to enlarge it.

The Durations and Errors table shows the metrics on how long the UI or API tests and their steps are performed on the tested service, and the number of various failures that occurred during the test run.

Low duration values are preferable, since the faster your service responds, the more requests per minute it can process.

The table includes the following columns:

Column Description
Script
Step Name
The name of the UI or API test, or test step.
Last duration The time it took virtual users to run the test or step last time, in seconds.
90th percentile duration This value indicates the maximum duration for 90% of tests or steps, in seconds. For each of these tests and steps, the actual time may be less than this value, but not greater.
95th percentile duration This value indicates the maximum duration for 95% of tests or steps, in seconds. For each of these tests and steps, the actual time may be less than this value, but not greater.
Average duration The average time it took virtual users to perform a test or step on the tested service, in seconds.
Minimum duration The minimum time it took virtual users to perform a UI or API test or step on the tested service, in seconds.
Maximum duration The maximum time it took virtual users to perform a UI or API test or step on the tested service, in seconds.
Standard duration The standard deviation of durations, in seconds.
Total Iterations The total number of iterations performed by all virtual users.
Total steps The total number of steps performed in the UI or API test by all virtual users.
Total failures The total number of errors all virtual users encountered during the test run.
Total assertion failures The number of validation failures that occurred during the run.
Total timeouts The number of timeout errors that occurred during the run.
Total page errors The number of page errors (for example, missing objects) that occurred during the test run.

The Average Navigation Times table shows the average time it took virtual users to navigate between the website’s pages and locate and identify objects there.

Navigation timings

LoadNinja counts the following navigation timings, one after another:

Load test structure

Each timing is counted separately. The total time is the overall duration of the load test.

The table includes the following columns:

Column Description
Script
Step Name
The name of the UI or API test, or test step.
Total time The average time it took to run the load test.
Think time The average time virtual users spent simulating pauses between user actions during the playback.
Redirect time The average time virtual users spent following the redirects until getting to the final URL if the tested website had responded with an HTTP 301 or 302 redirect.
DNS time The average time virtual users spent performing a DNS lookup, that is, obtaining the IP address of the website from a DNS server.
Connect time The average time virtual users spent performing a TCP handshake, that is, establishing a connection to the web server after the DNS lookup.
First byte time The average time virtual users spent waiting for the first byte of the response from the server. Its duration includes processing the requests, accessing the database of the server, selecting and generating a response, and depends on the server performance mostly.
Response time The average time passed from the moment when the client (a virtual user) sent the composed request until the moment the final byte was received.
DOM load time The average time it took to load and construct the DOM. The DOM is considered completed when the DOMContentLoaded event is triggered.
Event time The total time it took to fully load the page, as well as all the resources it refers to, to the Document Object Model (DOM). The page is considered fully loaded when the onload event is triggered.

See Also

Debug Virtual Users
Test Results

Highlight search results