Test Details: Error Page

1. Introduction

This guide provides a detailed walkthrough of the Error Page within the Test Details section. The Error Page allows users to analyze failed test requests, identify error causes, and take corrective actions. This document outlines how to navigate and utilize the Error Page effectively in Baseline 11.

2. System Requirements

To create a test, ensure you have:

• A stable internet connection

• An active Project Admin or Project Member account with AWS Setup

• A JMX file

• A web browser on a compatible device (PC, tablet, or mobile phone)

The steps mentioned below are the process for creating a test and provide details about the Error page

1

Accessing the Tests Page and Create a Test

1. Open your web browser

2. Go to our official website: www.baseline11.com

3. Sign in with your Project Admin or Project Member credentials

4. Navigate to the Dashboard

1. Click on the Tests tab

2. Click on the Add Test button

3. Upload your JMX File

1. Configure the test as required and You can add multiple Load Agents as per your plan limitation

1. Click Run Test to start execution

2. The test will now be listed in the Tests Table with its status updated in real-time

2

Monitoring Test Execution

1. The Baseline 11 platform provides real-time status updates of the test execution, including:

   • Test Summary (overall progress and key statistics)

   • Active Load Generator (LG) Details

   • Live Performance Metrics (Total thread, Total Request, Avg. response, 90% Avg. Overall TPS, error rate etc.)

   • Error Details

2. After clicking Run Test, you will be redirected to the Test Summary Page, where you can monitor your test in real-time.

3. Click on the Error Tab in the navigation bar to access the Error Page.

3

Summary Page

The Summary Page provides an overview of the test execution with key details displayed at the top:

• Test Name

• Number of Load Generators (LGs)

• Status (Initializing, Running, Failed, Cancelled)

• Total Duration

• Stop and Re-run Button

  • If the test is in Running status, the Stop Button is visible.

  • If the test is Completed, the Stop Button is replaced by the Re-run Button.

  

4

Sections on the Error Page

LG Name

• The LG Name section is located at the top right corner of the Summary Page, just below the key details section.

• It displays the selected LGs from the test creation phase.

• This section also functions as a filter—when specific LGs are selected, the displayed data updates accordingly in the main section.

Performance Metrics

Displays key metrics including:

• Total Failed Requests: The total number of requests that encountered errors.

• Error Rate (%) : The percentage of failed requests relative to the total executed requests.

• 2XX Error Count: The number of HTTP 2XX errors encountered, indicating unexpected behavior despite a successful response.

• 4XX Error Count: The number of HTTP 4XX errors, representing client-side request failures (e.g., 404 Not Found, 403 Forbidden).

• 5XX Error Count: The number of HTTP 5XX errors, indicating server-side issues (e.g., 500 Internal Server Error, 502 Bad Gateway).

• Non-HTTP Error Count: The number of failures unrelated to HTTP status codes, such as timeout errors, connection failures, or LG crashes.

Live Graphs

Displays real-time graphical representations of performance, including:

• Total Failed Requests Over Time:

  • Displays the count of failed requests plotted against time.

  • Helps identify periods with high failure rates.

• Total vs. Failed Requests Over Time:

  • Compares the total requests executed with the number of failed requests over time.

  • Useful for understanding failure trends relative to total execution.

• Error Transaction Response Time:

  • Graphs the response time of failed transactions.

  • Helps determine if errors are linked to slow response times.

• Error Transactions Per Second (TPS):

  • Displays the rate of failed transactions per second.

  • Indicates the frequency of errors occurring in the test execution.

  
• Expanding the Graph: You can expand any graph by clicking on the Expand Icon.

• Downloading the Graph: To download the graph as an image, click on the three dots icon and select the desired format (JPG or SVG) for downloading.

Table Data (Aggregate Report (All Requests))

Displays real-time data in table format (if there are no errors, the table will be empty), including:

• Label: Identifies the request or transaction name.

• # Samples: The total number of test samples (requests) executed.

• # Error Samples: The number of requests that encountered errors.

• Error (%): The percentage of failed requests compared to total requests.

• Average: The mean response time for the given request.

• Min: The shortest response time recorded.

• Max: The longest response time recorded.

• Throughput: The number of requests processed per second.

• 90% Line: The response time below which 90% of requests fall.

• 95% Line: The response time below which 95% of requests fall.

• 99% Line: The response time below which 99% of requests fall.

• Received Bytes: The total amount of data received during test execution.

• Sent Bytes: The total amount of data sent during test execution.

Downloading the Table: To download the entire table as CSV click on the Export button and click on the Download as CSV

Error-Specific Details

There is another table visible if errors occur during test execution. This table categorizes errors based on HTTP status codes such as 2XX, 4XX, 5XX, and Non-HTTP errors. It helps users analyze specific types of errors and their frequency.

This table shares details below:

• Transaction: Represents the failed request or operation.

• Load Agent ID: Identifies the LG associated with the error.

• Response Code: Displays the HTTP status code or error identifier.

• Error Message: Provides details on the nature of the error.

• Count: Indicates the number of times the error has occurred.

3. Troubleshooting

• Test failed to execute? Check the status’s information icon for errors and reconfigure if necessary.

• Results not loading? Refresh the page or clear the cache.

• Rerun not working? Ensure the test meets rerun criteria.