Updates based on PR auto-check warnings

Nagarjuna-Vipparthi · web-flow · commit 83bf535b8a87 · 2025-02-27T21:06:21.000+05:30
diff --git a/articles/load-testing/concept-load-testing-concepts.md b/articles/load-testing/concept-load-testing-concepts.md
@@ -113,7 +113,7 @@ A test run represents one execution of a load test. When you run a test, the tes
 
 After the test run completes, you can [view and analyze the load test results in the Azure Load Testing dashboard](./tutorial-identify-bottlenecks-azure-portal.md) in the Azure portal. 
 
-Alternately, you can [download the test logs](./how-to-diagnose-failing-load-test.md#download-apache-jmeter-worker-logs-for-your-load-test) and [export the test results file](./how-to-export-test-results.md).
+Alternately, you can [download the test logs](./how-to-diagnose-failing-load-test.md#download-apache-jmeter-or-locust-worker-logs-for-your-load-test) and [export the test results file](./how-to-export-test-results.md).
 
 > [!IMPORTANT]
 > When you update a test, the existing test runs don't automatically inherit the new settings from the test. The new settings are only used by new test runs when you run the *test*. If you rerun an existing *test run*, the original settings of the test run are used.
diff --git a/articles/load-testing/how-to-diagnose-failing-load-test.md b/articles/load-testing/how-to-diagnose-failing-load-test.md
@@ -97,7 +97,7 @@ A load test can fail to complete because of multiple reasons. Examples of why a
 Use the following steps to help diagnose a test not finishing:
 
 1. Verify the error details on the load test dashboard.
-1. [Download and analyze the test logs](#download-apache-jmeter-worker-logs-for-your-load-test) to identify issues in the JMeter test script.
+1. [Download and analyze the test logs](#download-apache-jmeter-or-locust-worker-logs-for-your-load-test) to identify issues in the JMeter test script.
 1. [Download the test results](./how-to-export-test-results.md) to identify issues with individual requests.
 
 ### Load test completed
diff --git a/articles/load-testing/how-to-export-test-results.md b/articles/load-testing/how-to-export-test-results.md
@@ -45,7 +45,7 @@ timeStamp,elapsed,label,responseCode,responseMessage,threadName,dataType,success
 After a load test run finishes, you can access and download the load test results and the HTML report through the Azure portal, or as an artifact in your CI/CD workflow.
 
 >[!IMPORTANT]
->For load tests with more than 45 engine instances or a greater than 3-hour test run duration, the results file is not available for download. You can [configure a JMeter Backend Listener to export the results](#export-test-results-using-jmeter-backend-listeners) to a data store of your choice or [copy the results from a storage account container](#copy-test-artifacts-from-a-storage-account-container).
+>For load tests with more than 45 engine instances or a greater than 3-hour test run duration, the results file is not available for download. You can [configure a JMeter Backend Listener to export the results](#export-test-results-using-listeners) to a data store of your choice or [copy the results from a storage account container](#copy-test-artifacts-from-a-storage-account-container).
 >For tests with samplers greater than 30, the downloaded HTML report will only have graphs for data aggregated over all samplers. Graphs will not show sampler-wise data. Additionally, the downloaded report doesn't support graphs corresponding to server-side metrics.
 
 # [Azure portal](#tab/portal)
diff --git a/articles/load-testing/how-to-high-scale-load.md b/articles/load-testing/how-to-high-scale-load.md
@@ -149,7 +149,7 @@ To specify the load parameters for a JMeter-based load test:
 
 1. On the **Edit test** page, select the **Load** tab. Use the **Engine instances** slider control to update the number of test engine instances, or enter the value directly in the input box.
 
-    :::image type="content" source="media/how-to-high-scale-load/edit-test-load.png" alt-text="Screenshot of the 'Load' tab on the 'Edit test' pane." lightbox="media/how-to-high-scale-load/edit-test-load.png":::
+    :::image type="content" source="media/how-to-high-scale-load/edit-test-load.png" alt-text="Screenshot of the 'Load' tab on the 'Edit test' pane for JMeter-based tests." lightbox="media/how-to-high-scale-load/edit-test-load.png":::
 
 1. Select **Apply** to modify the test and use the new configuration when you rerun it.
 
@@ -195,7 +195,7 @@ To specify the load parameters for a Locust-based load test:
 1. On the **Edit test** page, select the **Load** tab. Enter the values for the overall users required and overall spwan rate in the respective input boxes. 
 The engine instance count required to generate this load is automatically populated. If your test script is complex and resource intensive, use the **Engine instances** slider control to update the number of test engine instances, or enter the value directly in the input box.
 
-    :::image type="content" source="media/how-to-high-scale-load/edit-test-load-locust.png" alt-text="Screenshot of the 'Load' tab on the 'Edit test' pane." lightbox="media/how-to-high-scale-load/edit-test-load-locust.png":::
+    :::image type="content" source="media/how-to-high-scale-load/edit-test-load-locust.png" alt-text="Screenshot of the 'Load' tab on the 'Edit test' pane for Locust-based tests." lightbox="media/how-to-high-scale-load/edit-test-load-locust.png":::
 
 Alternatively, you can configure the number of users and spawn rate in the test script or Locust configuration file and provide the number of engine instances required. 
 
@@ -277,9 +277,7 @@ To achieve a target number of requests per second, configure the total number of
 > [!NOTE]
 > Apache JMeter only reports requests that made it to the server and back, either successful or not. If Apache JMeter is unable to connect to your application, the actual number of requests per second will be lower than the maximum value. Possible causes might be that the server is too busy to handle the request, or that a TLS/SSL certificate is missing. To diagnose connection problems, you can check the **Errors** chart in the load testing dashboard and [download the load test log files](./how-to-diagnose-failing-load-test.md).
 
-## Test engine instances and virtual users
-
-# [Apache JMeter](#tab/jmeter)
+## Test engine instances and virtual users for JMeter-based tests
 
 In the Apache JMeter script, you can specify the number of parallel threads. Each thread represents a virtual user that accesses the application endpoint. We recommend that you keep the number of threads in a script below a maximum of 250.
 
@@ -293,7 +291,7 @@ For example, to simulate 1,000 virtual users, set the number of threads in the A
 
 The location of the Azure Load Testing resource determines the location of the test engine instances. All test engine instances within a Load Testing resource are hosted in the same Azure region.
 
-# [Locust](#tab/locust)
+## Test engine instances and virtual users for Locust-based tests
 
 Configure the total number of users required for your load test. This represents the peak number of concurrent Locust users. You can configure this in the load configuration while creating a test in Azure Load Testing. You can also configure this in your test script or the Locust configuration file. We recommend running upto 500 users from a test engine instance.
 
diff --git a/articles/load-testing/how-to-parameterize-load-tests.md b/articles/load-testing/how-to-parameterize-load-tests.md
@@ -265,6 +265,7 @@ You first define a user-defined variable that reads the environment variable, an
     ```xml
     <stringProp name="HTTPSampler.domain">${udv_webapp}</stringProp>
     ```
+    
 # [Locust](#tab/locust)
 
 1. Initialize a variable with the environment variable's value using the *Name* specified in the load test configuration. 
diff --git a/articles/load-testing/how-to-read-csv-data.md b/articles/load-testing/how-to-read-csv-data.md
@@ -35,9 +35,7 @@ In this section, you configure your test script to reference the external CSV fi
 > [!IMPORTANT]
 > Azure Load Testing uploads the JMX file and all related files in a single folder. When you reference an external file in your JMeter script, verify that you have no file path references in your test script.
 
-# [Apache JMeter](#tab/jmeter)
-
-Modify the JMeter script by using the Apache JMeter GUI:
+For JMeter-based tests, modify the JMeter script by using the Apache JMeter GUI:
 
 1. Select the **CSV Data Set Config** element in your test script.
 
@@ -53,9 +51,7 @@ Modify the JMeter script by using the Apache JMeter GUI:
 
 1. Save the JMeter script and upload the script to your load test.
 
-# [Locust](#tab/locust)
-
-Modify the Locust script by opening it an editor of your choice. 
+For Locust-based tests, update the Locust script by opening it an editor of your choice. 
 
 1. In the section where you open the file, update the **Filename** information and remove any file path reference.
 
@@ -130,7 +126,7 @@ For example, if you have a large customer CSV input file, and the load test runs
 
 > [!IMPORTANT]
 > Azure Load Testing doesn't preserve the header row when splitting your CSV file. 
-> 1. [Configure your test script](#update-your-jmeter-script-to-read-csv-data) to use variable names when reading the CSV file. 
+> 1. [Configure your test script](#update-your-test-script-to-read-csv-data) to use variable names when reading the CSV file. 
 > 1. Remove the header row from the CSV file before you add it to the load test.
 
 To configure your load test to split input CSV files:
@@ -173,7 +169,7 @@ To configure your load test to split input CSV files:
 
 ### Test status is failed and test log has `File {my-filename} must exist and be readable`
 
-When the load test completes with the Failed status, you can [download the test logs](./how-to-diagnose-failing-load-test.md#download-apache-jmeter-worker-logs-for-your-load-test).
+When the load test completes with the Failed status, you can [download the test logs](./how-to-diagnose-failing-load-test.md#download-apache-jmeter-or-locust-worker-logs-for-your-load-test).
 
 When you receive an error message `File {my-filename} must exist and be readable` in the test log, the input CSV file couldn't be found when running the test script.
 
diff --git a/articles/load-testing/how-to-test-secured-endpoints.md b/articles/load-testing/how-to-test-secured-endpoints.md
@@ -130,11 +130,9 @@ The following code snippet gives an example of how to configure a load test secr
 ```
 ---
 
-### Retrieve and use the secret value in the test script
+### Retrieve and use the secret value in the JMeter script
 
-You can now retrieve the secret value in the test script and pass it to the application request. For example, use an `Authorization` HTTP header to pass an OAuth token to a request. 
-
-# [Apache JMeter](#tab/jmeter)
+You can now retrieve the secret value in the JMeter script by using the `GetSecret` custom function and pass it to the application request. For example, use an `Authorization` HTTP header to pass an OAuth token to a request. 
 
 1. Create a user-defined variable that retrieves the secret value with the `GetSecret` custom function:
 
@@ -148,7 +146,9 @@ You can now retrieve the secret value in the test script and pass it to the appl
 
     :::image type="content" source="./media/how-to-test-secured-endpoints/jmeter-add-http-header.png" alt-text="Screenshot that shows how to add an authorization header to a request in JMeter." lightbox="./media/how-to-test-secured-endpoints/jmeter-add-http-header.png":::
 
-# [Locust](#tab/locust)
+### Retrieve and use the secret value in the Locust script
+
+You can now retrieve the secret value in the Locust script and pass it to the application request. For example, use an `Authorization` HTTP header to pass an OAuth token to a request. 
 
 The secrets configured in the load test configuration are accessible as environment variables. 
 
