Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us540458-13

Author: TimShererWithAquent

articles/app-service/includes/quickstart-python/virtual-environment-setup.md

@@ -7,14 +7,14 @@ ms.service: azure-app-service
 ---
 #### [Windows](#tab/windows)
 
-```Console
+```cmd
 py -m venv .venv
 .venv\scripts\activate
 ```
 
 #### [macOS/Linux](#tab/mac-linux)
 
-```Bash
+```bash
 python3 -m venv .venv
 source .venv/bin/activate
 ```

articles/app-service/tutorial-python-postgresql-app-fastapi.md

@@ -120,6 +120,8 @@ landingContent:
     linkLists:
       - linkListType: how-to-guide
         links:
+          - text: Analyze tests using the results dashboard
+            url: load-testing/how-to-understand-test-run-results-dashboard.md
           - text: Compare load test runs
             url: load-testing/how-to-compare-multiple-test-runs.md
           - text: Analyze results using AI insights

articles/app-testing/index.yml

@@ -12,13 +12,13 @@ ms.topic: how-to
 
 # Compare load test runs in Azure Load Testing
 
-In this article, you learn how you can compare test runs in Azure Load Testing. You can view trends across the last 10 test runs, or you can select and compare up to ten individual test runs. Optionally, you can mark a test run as a baseline to compare against.
+In this article, you learn how you can compare test runs in Azure Load Testing. You can view trends across the last few test runs, or you can select and compare up to 10 individual test runs. Optionally, you can mark a test run as a baseline to compare against.
 
-To identify regressions over time, you can use the client-side metrics trends of the last 10 test runs, such as the response time, error rate, and more. In combination with [CI/CD integration](./quickstart-add-load-test-cicd.md), the trends data might help you identify which application build introduced a performance issue.
+To identify regressions over time, you can use the client-side metrics trends of the previous test runs, such as the response time, error rate, and more. In combination with [CI/CD integration](./quickstart-add-load-test-cicd.md), the trends data might help you identify which application build introduced a performance issue.
 
 When you want to compare the client-side metrics trends against a specific reference test run, you can mark that test run as your baseline. For example, before you implement performance optimizations in your application, you might first create a baseline load test run, and then validate the effects of your optimizations against your baseline.
 
-To compare both client-side and server-side metrics, you can select up to ten test runs, and compare them in the Azure Load Testing dashboard. The dashboard overlays the client-side and server-side metric graphs for each test run. By also comparing server-side application metrics in the dashboard, you can identify which application component was the root cause for a sudden performance degradation.
+To compare both client-side and server-side metrics, you can select up to 10 test runs, and compare them in the Azure Load Testing dashboard. The dashboard overlays the client-side and server-side metric graphs for each test run. By also comparing server-side application metrics in the dashboard, you can identify which application component was the root cause for a sudden performance degradation.
 
 ## Prerequisites
 
@@ -28,9 +28,9 @@ To compare both client-side and server-side metrics, you can select up to ten te
 
 ## Compare multiple load test runs
 
-To compare test runs in Azure Load Testing, you first have to select up to ten runs within a load test. You can only compare runs that belong to the same load test. After you select the test runs you want to compare, you can visually compare the client-side and server-side metrics for each test run in the load test dashboard.
+To compare test runs in Azure Load Testing, you first have to select up to 10 runs. These test runs can be from the same load test or from another load test. After you select the test runs you want to compare, you can visually compare the client-side and server-side metrics for each test run in the load test dashboard.
 
-A test run needs to be in the *Done*, *Stopped*, or *Failed* state to compare it.
+A test run needs to be in the *Passed*, *Failed*, *Completed*, or *Stopped* state to compare it.
 
 Use the following steps to select the test runs:
 
@@ -45,7 +45,7 @@ Use the following steps to select the test runs:
 
 1. Select two or more test runs, and then select **Compare** to compare test runs.
 
-    You can choose a maximum of ten test runs to compare.
+    You can choose a maximum of 10 test runs to compare.
 
     :::image type="content" source="media/how-to-compare-multiple-test-runs/compare-test-results-from-list.png" alt-text="Screenshot that shows a list of test runs and the 'Compare' button in the Azure portal." lightbox="media/how-to-compare-multiple-test-runs/compare-test-results-from-list.png":::
 
@@ -58,9 +58,11 @@ Use the following steps to select the test runs:
 
     :::image type="content" source="media/how-to-compare-multiple-test-runs/load-test-dashboard-compare-runs.png" alt-text="Screenshot of the load testing dashboard in the Azure portal, comparing two test runs." lightbox="media/how-to-compare-multiple-test-runs/load-test-dashboard-compare-runs.png":::
 
+1. Optionally, you can change the test runs selected for comparison by selecting 'Update selection'. You can select test runs from the same load test or from a different one.
+
 ## View metrics trends across load test runs
 
-To view metrics trends across test runs in Azure Load Testing, you need to have at least two test runs in the *Done*, or *Stopped* state. You can only view trends from runs that belong to the same load test.
+To view metrics trends across test runs in Azure Load Testing, you need to have at least two test runs in *Passed*, *Failed*, *Completed*, or *Stopped* state. You can only view trends from runs that belong to the same load test.
 
 Use the following steps to view metrics trends across test runs:
 

articles/app-testing/load-testing/how-to-compare-multiple-test-runs.md

@@ -14,13 +14,7 @@ ms.topic: how-to
 
 In this article, you learn how to diagnose and troubleshoot failing load tests in Azure Load Testing. Azure Load Testing provides several options to identify the root cause of a failing load test. For example, you can use the load test dashboard, or download the test results or test log files for an in-depth analysis. Alternately, configure server-side metrics to identify issues with application endpoint.
 
-Azure Load Testing uses two indicators to determine the outcome of a load test:
-
-- **Test status**: indicates whether the load test was able to start successfully and run the test script until the end. For example, the test status is *Failed* if there's an error in the JMeter or Locust test script, or if the [autostop listener](./how-to-define-test-criteria.md#auto-stop-configuration) interrupted the load test because too many requests failed.
-
-- **Test result**: indicates the result of evaluating the [test fail criteria](./how-to-define-test-criteria.md). If at least one of the test fail criteria was met, the test result is set to *Failed*.
-
-Depending on the indicator, you can use a different approach to identify the root cause of a test failure.
+Azure Load Testing uses the test run status to determine the outcome of a load test. Depending on the indicator, you can use a different approach to identify the root cause of a test failure. For more details on test run status, see [Analyze load tests using the results dashboard](./how-to-understand-test-run-results-dashboard.md#test-run-details)
 
 ## Prerequisites  
 
@@ -39,7 +33,7 @@ Use the following steps to get the outcome of a load test:
 
 1. Select a test from the list to view all test runs for that test.
 
-    The list of test runs shows the **Test result** and **Test status** fields.
+    The list of test runs shows the **Status** field.
 
     :::image type="content" source="media/how-to-find-download-logs/load-testing-test-runs-list.png" alt-text="Screenshot that shows the list of test runs in the Azure portal, highlighting the test result and test status columns." lightbox="media/how-to-find-download-logs/load-testing-test-runs-list.png":::
 
@@ -85,20 +79,21 @@ You can use a different approach for diagnosing a load test failure based whethe
 
 ### Load test failed to complete
 
-When the load test fails to complete, the *test status* of the test run is set to *Failed*.
+When the load test fails to complete, the *status* of the test run is set to *Error* or *Stopped*.
 
 A load test can fail to complete because of multiple reasons. Examples of why a load test doesn't finish:
 
 - There are errors in the test script.
 - The test script uses JMeter features that Azure Load Testing doesn't support. Learn about the [supported JMeter features](./resource-jmeter-support.md).
 - The test script references a file or plugin that isn't available on the test engine instance.
-- The autostop functionality interrupted the load test because too many requests are failing and the error rate exceeds the threshold. Learn more about the [autostop functionality in Azure Load Testing](./how-to-define-test-criteria.md#auto-stop-configuration).
+- The auto-stop functionality interrupted the load test because too many requests are failing and the error rate exceeds the threshold. Learn more about the [autostop functionality in Azure Load Testing](./how-to-define-test-criteria.md#auto-stop-configuration).
 
 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-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.
+1. Run the test in [debug mode](./how-to-run-tests-in-debug-mode.md) to get debug logs and request and response data for failed requests. 
 
 You can also view AI-based error insights for your test run after a test run completes. The insights generated contain the cause of error and more actionable recommendations. This feature is turned on by default and can be turned off in the error blade settings. Refer to [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839).
 
@@ -107,7 +102,7 @@ You can also view AI-based error insights for your test run after a test run com
 
 ### Load test completed
 
-A load test might run the test script until the end (test status equals *Done*), but might not pass all the [test fail criteria](./how-to-define-test-criteria.md). If at least one of the test criteria didn't pass, the *test result* of the test run is set to *Failed*.
+A load test might run the test script until the end, but might not pass all the [test fail criteria](./how-to-define-test-criteria.md). If at least one of the test criteria didn't pass, the *status* of the test run is set to *Failed*.
 
 Use the following steps to help diagnose a test failing to meet the test criteria:
 
@@ -135,7 +130,9 @@ To download the worker logs for an Azure Load Testing test run, follow these ste
 
 1. From the list of test runs, select a test run to view the load test dashboard.
 
-1. On the dashboard, select **Download**, and then select **Logs**.
+1. On the dashboard, select **Download**, and then select **Logs**. To view the logs in Azure portal, select **View**. You can view the files in the storage container, select the required file and view the file. If the file format is not supported for viewing, you can select **Download** to download the specific file. 
+
+1. To download the logs files as a zipped folder, select **Download**. 
 
     The browser should now start downloading a zipped folder that contains the JMeter or Locust worker node log file for each [test engine instance](./concept-load-testing-concepts.md#test-engine).
 

articles/app-testing/load-testing/how-to-diagnose-failing-load-test.md

@@ -12,7 +12,7 @@ ms.topic: how-to
 ---
 # Export test results from Azure Load Testing for use in third-party tools
 
-In this article, you learn how to export your Azure Load Testing test results and reports. You can download the results by using the Azure portal, as an artifact in your CI/CD workflow, in JMeter by using a backend listener, in Locust by using event hooks or listener plugins,  or by copying the results from an Azure storage account. You can use these results for reporting in third-party tools or for diagnosing test failures. Azure Load Testing generates the test results in comma-separated values (CSV) file format, and provides details of each application request for the load test.
+In this article, you learn how to export your Azure Load Testing test results and reports. You can view the results in the Azure portal, download the results using the Azure portal, as an artifact in your CI/CD workflow, in JMeter by using a backend listener, in Locust by using event hooks or listener plugins, or by copying the results from an Azure storage account. You can use these results for reporting in third-party tools or for diagnosing test failures. Azure Load Testing generates the test results in comma-separated values (CSV) file format, and provides details of each application request for the load test.
 
 You can also use the test results to diagnose errors during a load test. The `responseCode` and `responseMessage` fields give you more information about failed requests. For more information about investigating errors, see [Diagnose failing load tests](./how-to-diagnose-failing-load-test.md).
 
@@ -40,17 +40,17 @@ timeStamp,elapsed,label,responseCode,responseMessage,threadName,dataType,success
 1676040230680,101,Homepage,200,OK,172.18.33.7-Thread Group 1-1,text,true,,1591,133,5,5,https://www.example.com/,98,0,94
 ```
 
-## Access and download load test results and report
+## View and download load test results and report
 
-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.
+After a load test run finishes, you can view 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-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)
 
-To download the test results and the HTML report for a test run in the Azure portal:
+To view and download the test results and the HTML report for a test run in the Azure portal:
 
 1. In the [Azure portal](https://portal.azure.com), go to your Azure Load Testing resource.
 
@@ -65,14 +65,18 @@ To download the test results and the HTML report for a test run in the Azure por
 
    * Select the ellipsis (**...**) next to the load test run you're working with, and then select **Download results file**.
 
-     :::image type="content" source="media/how-to-export-test-results/test-run-page-download.png" alt-text="Screenshot that shows how to download the results file for a load test run.":::  
+     :::image type="content" source="media/how-to-export-test-results/test-run-page-download.png" alt-text="Screenshot that shows how to download the results file for a load test run." lightbox="media/how-to-export-test-results/test-run-page-download.png":::  
 
      > [!NOTE]
-     > A load test run needs to have a *Done*, *Stopped*, or *Failed* status for the results file to be available for download.
+     > A load test run needs to have a *Passed*, *Failed*, *Completed*, or *Stopped* status for the results file to be available for download.
 
-   * Select **Download** on the **Test run details** pane. To download the results, select **Results**. To download the HTML report, select **Report**.
+   * Select **Download** on the **Test run details** pane. To download the results, select **Results** and select **Download**. To download the HTML report, select **Report**.
 
-     :::image type="content" source="media/how-to-export-test-results/download-dashboard.png" alt-text="Screenshot that shows how to download the test results from the 'Test run details' pane.":::
+     :::image type="content" source="media/how-to-export-test-results/download-dashboard.png" alt-text="Screenshot that shows how to download the test results from the 'Test run details' pane." lightbox="media/how-to-export-test-results/download-dashboard.png":::
+
+   * To view the results files in the storage container, select **Download** on the **Test run details** pane, select **Results** and select **View**. You can view the results files from all the test engines in the right context pane. Select the file that you want to download and select **Download**. 
+
+     :::image type="content" source="media/how-to-export-test-results/view-results-file.png" alt-text="Screenshot that shows how to view the test results from the 'Test run details' pane." lightbox="media/how-to-export-test-results/view-results-file.png":::
 
 1. You can use any zip tool to extract the folder and access the downloaded files.
 
@@ -177,14 +181,14 @@ To copy the test results and log files for a test run from a storage account, in
    >[!TIP]
    > To limit the number of tests to display in the list, you can use the search box and the **Time range** filter.
 
-1. On the **Test run details** pane, select **Copy artifacts**.
+1. On the **Test run details** pane, select **Download**, then select **Results** and select **View**. You can see the storage container view with the results files. 
 
      :::image type="content" source="media/how-to-export-test-results/test-run-page-copy-artifacts.png" alt-text="Screenshot that shows how to copy the test artifacts from the 'Test run details' pane.":::
 
      > [!NOTE]
      > A load test run needs to be in the *Done*, *Stopped*, or *Failed* status for the results file to be available for download.
 
-1. Copy the SAS URL of the storage account container. 
+1. Select **Copy SAS URL** to copy the SAS URL of the storage account container. 
 
     You can use the SAS URL in the [Azure Storage Explorer](/azure/vs-azure-tools-storage-manage-with-storage-explorer?tabs=windows#shared-access-signature-sas-url) or [AzCopy](/azure/storage/common/storage-use-azcopy-blobs-copy#copy-a-container) to copy the results CSV files and the log files for the test run to your storage account.
 

articles/app-testing/load-testing/how-to-export-test-results.md

@@ -229,6 +229,7 @@ For CI/CD workflows, you configure the number of engine instances in the [YAML t
 
 1. Save the YAML configuration file, and commit the changes to source control.
 
+---
 
 ## Monitor engine instance metrics