# Test Details Summary Page

<details>

<summary>1. Introduction</summary>

This guide provides a detailed overview of the Summary Page within the Test Details section. The Summary Page is a crucial component that allows users to monitor test execution, analyze results. This document outlines how to navigate and utilize the Summary Page effectively in Baseline 11.

</details>

<details>

<summary>2. System Requirements</summary>

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)

</details>

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

{% stepper %}
{% step %}

## Accessing the Tests Page and Create a Test <a href="#toc193733620" id="toc193733620"></a>

1. Open your web browser
2. Go to our official website: [www.baseline11.com](https://www.baseline11.com/)
3. Sign in with your Project Admin or Project Member credentials
4. Navigate to the Dashboard

<figure><img src="/files/D6iHU46ZOKlKu27MAADy" alt=""><figcaption></figcaption></figure>

5. Click on the Tests tab
6. Click on the **Add Test** button
7. Upload your **JMX File**

<figure><img src="/files/nmZIGvryMYWtHq7swt6Q" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/9FPwej7fEnjSXt72omPl" alt=""><figcaption></figcaption></figure>

9. Click **Run Test** to start execution
10. The test will now be listed in the **Tests Table** with its status updated in real-time
    {% endstep %}

{% step %}

## **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 threads, Total Requests, Average Response Time, 90% Response Time, 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.
   {% endstep %}

{% step %}

## **Summary Section**

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**.

  <figure><img src="/files/NNRiab3pUXUw5WQV7H4C" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

## **Sections on the Summary Page**

{% tabs %}
{% tab title="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.

<figure><img src="/files/KELpKcAcQnIRUFtI5cbj" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Performance Metrics" %}
Displays key metrics including:

* **Total Threads**: Number of active users in the test.
* **Total Requests**: The total number of HTTP requests processed.
* **Average Response Time**: The mean response time for requests.
* **90% Response Time**: The response time for 90% of requests.
* **Overall TPS (Transactions Per Second)**: Indicates the system's efficiency in handling transactions.
* **Error Percentage**: Shows the percentage of failed requests.

<figure><img src="/files/AiUnV5IHKuEHOwDKLPEC" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Live Graphs" %}
Displays real-time graphical representations of performance, including:

* **Active Users**: Displays the number of virtual users currently active in the test. This helps monitor load distribution.
* **Throughput**: Measures the number of requests processed per second. Higher throughput generally indicates better system performance.
* **Bytes Throughput**: Shows the amount of data (in bytes) being transferred per second. It helps analyze network bandwidth consumption.
* **Average Response Time (s)**: Represents the average time taken for requests to complete. Lower values indicate better performance.
* **Transaction Response Time**: Measures the response time for individual transactions. It provides insights into how long different requests take.
* **Transactions Per Second (TPS)**: Indicates the number of transactions processed per second. Higher TPS values show better system efficiency.

<figure><img src="/files/HowJOdMPPd9VgCVqnt44" alt=""><figcaption></figcaption></figure>

* **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.

<figure><img src="/files/JAVwNfDd0q6hTSIcCdjC" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Table Data (Aggregate Report (All Requests))" %}
Displays real-time data in table format, including:

* **Samples**: Represents the total number of requests executed during the test.
* **Error Samples**: Displays the number of failed requests, helping identify test reliability issues.
* **Error %**: Shows the percentage of failed requests compared to total samples. A lower error rate indicates better system performance.
* **Average**: Calculates the mean response time of all requests. This helps gauge general application responsiveness.
* **Min**: Displays the fastest response time recorded during the test.
* **Max**: Shows the slowest response time recorded, useful for detecting bottlenecks.
* **Throughput**: Measures the number of requests handled per second, indicating system efficiency under load.
* **90% Line**: Indicates the response time within which 90% of requests were completed.
* **95% Line**: Indicates the response time within which 95% of requests were completed.
* **99% Line**: Indicates the response time within which 99% of requests were completed.
* **Received Bytes**: Represents the total data received from the server during the test.

<figure><img src="/files/6xfnr2ahcMaMyIQOWsX5" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/aKE50Deop8yeXKOXFKMR" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}
{% endstep %}
{% endstepper %}

<details>

<summary>3. Troubleshooting</summary>

* **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.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://baseline11.gitbook.io/quick-guide/test-details/test-details-summary-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.