> For the complete documentation index, see [llms.txt](https://baseline11.gitbook.io/quick-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://baseline11.gitbook.io/quick-guide/test-details/test-details-config-page.md).

# Test Details Config Page

<details>

<summary>1. Introduction</summary>

Test Details Config Page provides details of the test setup after execution. It includes key information such as test details, JMeter configuration, Load Agent details, and JMeter Plugins used in the test. This page is essential for verifying all configurations after running a performance test. Users can review and confirm that all settings are correctly applied to avoid execution issues.

</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 Test Details Config page

{% stepper %}
{% step %}

## Accessing the Tests Page and Create a Test <a href="#toc193810697" id="toc193810697"></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="https://3076107135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDJ8r3jxpSQ88OP2q1Q6%2Fuploads%2F1AeSZcz7Ry17uxqgvDyK%2Fimage.png?alt=media&amp;token=a7b82bba-dd27-4f14-a506-4373563509d6" 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="https://3076107135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDJ8r3jxpSQ88OP2q1Q6%2Fuploads%2F4A1FEC4PdLm8ykfoRnhv%2Fimage.png?alt=media&amp;token=7ca59f8d-ee0c-4ecf-9d6d-4becbbe36fac" 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="https://3076107135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDJ8r3jxpSQ88OP2q1Q6%2Fuploads%2FwRogWW1IGFnSRw4pF7V0%2Fimage.png?alt=media&amp;token=f3fdc6b2-a7fd-48b4-a6ca-6e97a4ae2d65" 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 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 **Test Details Config** Tab in the navigation bar to access the Test Details Config.
   {% endstep %}

{% step %}

## **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**.&#x20;

  <figure><img src="https://3076107135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDJ8r3jxpSQ88OP2q1Q6%2Fuploads%2FgRq9e3tRf1E5n4kA5x1X%2Fimage.png?alt=media&amp;token=1278021f-8cd0-4826-add0-d4e91be3b4fc" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

## **Sections on the** Test Details Config **Page**

{% tabs %}
{% tab title="Test Details" %}
You can see the details of the test that you have configured before execution. These details include:

* **Test Name**: The name assigned to the test.
* **Test ID**: A unique identifier for the test.
* **Start Time**: The scheduled or actual start time of the test.
* **End Time**: The expected or actual end time of the test.
* **Test Duration**: The total time the test is set to run.
* **User**: The account that initiated the test.
* **Project Name**: The project associated with the test.
* **Description**: Additional notes or descriptions about the test.

<figure><img src="https://3076107135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDJ8r3jxpSQ88OP2q1Q6%2Fuploads%2FfbI3q5yZuzsG2TRWB3Vc%2Fimage.png?alt=media&amp;token=0009d2b6-45c4-4a05-9ed4-638d3384e79c" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="JMeter Configuration" %}
This section displays the JMeter-related configurations applied before test execution.

* **JMeter Version**: Specifies the version of JMeter used for the test.
* **JMX File**: The test script uploaded for execution.
* **Extra Files**: Any additional files required for the test (these can be downloaded by clicking on the file name).
* **Spit Option**:

  * The **Split Option** in the Extra Files section determines how the uploaded CSV file is handled during test execution:
  * If "**Split**" is **checked** during CSV upload, the system distributes the CSV file across multiple Load Generators (LGs). The UI will display "**Split**",
  * If "**Split**" is **not checked**, the file remains unsplit, meaning each LG will access the entire file instead of a distributed portion. The UI will display "**Not Split**"
  * This feature is useful in scenarios where test data needs to be **evenly distributed** among multiple LGs for efficient load testing.

  <figure><img src="https://3076107135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDJ8r3jxpSQ88OP2q1Q6%2Fuploads%2FrcPmrRnapxTf9h2DycmU%2Fimage.png?alt=media&amp;token=328044ac-8e7f-475f-8ccf-916cbe506567" alt=""><figcaption></figcaption></figure>

{% endtab %}

{% tab title="Load Agent Details" %}
If you have added the Load Agent before executing the test, these details are displayed in a table format. This section provides comprehensive insights into the Load Agents assigned to the test, ensuring users can monitor and manage their distributed testing environment effectively. Details include:

* **Location**: The geographical region where the Load Agent is hosted.
* **Type**: The instance type used for the Load Agent.
* **vCPU Count**: The number of virtual CPUs assigned to the Load Agent.
* **Size**: The memory and processing capacity of the Load Agent.
* **Subnet**: The network subnet in which the Load Agent operates.
* **Instance ID**: The unique identifier assigned to the Load Agent.
* **Start Time**: The timestamp when the Load Agent was initialized.
* **Termination Time**: The timestamp when the Load Agent was stopped or removed.
  * If the specific instance is not terminated, then in this termination time's cell, an error message appears to close the instance from AWS.)
    {% endtab %}

{% tab title="JMeter Plugins" %}
If the user has selected any plugins before test execution, they will be displayed here along with their respective versions.

<figure><img src="https://3076107135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDJ8r3jxpSQ88OP2q1Q6%2Fuploads%2FMoPqXLBXwbpPQHEHHzo9%2Fimage.png?alt=media&amp;token=f7d46fd0-53e2-4964-ac27-c05ecf0b17cf" 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>