You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/load-testing/how-to-export-test-results.md
+19-14Lines changed: 19 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,12 +12,14 @@ ms.topic: how-to
12
12
---
13
13
# Export test results from Azure Load Testing for use in third-party tools
14
14
15
-
In this article, you learn how to export your Azure Load Testing test results. 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, or by copying the results from an Azure storage account. You might 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.
15
+
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, 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.
16
16
17
17
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).
18
18
19
19
You can generate the Apache JMeter dashboard from the CSV log file following the steps mentioned [here](https://jmeter.apache.org/usermanual/generating-dashboard.html#report).
20
20
21
+
You can also download the Azure Load Testing Result dashboard as an HTML report for offline viewing and collaboration.
22
+
21
23
## Prerequisites
22
24
23
25
- An Azure account with an active subscription. If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
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
39
41
```
40
42
41
-
## Access and download load test results
43
+
## Access and download load test results and report
42
44
43
-
After a load test run finishes, you can access and download the load test results through the Azure portal, or as an artifact in your CI/CD workflow.
45
+
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.
44
46
45
47
>[!IMPORTANT]
46
-
>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).
48
+
>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).
49
+
>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 will only show graphs corresponding to client-side metrics.
47
50
48
51
# [Azure portal](#tab/portal)
49
52
50
-
To download the test results for a test run in the Azure portal:
53
+
To download the test results and the HTML report for a test run in the Azure portal:
51
54
52
55
1. In the [Azure portal](https://portal.azure.com), go to your Azure Load Testing resource.
53
56
@@ -67,19 +70,21 @@ To download the test results for a test run in the Azure portal:
67
70
> [!NOTE]
68
71
> A load test run needs to have a *Done*, *Stopped*, or *Failed* status for the results file to be available for download.
69
72
70
-
*On the **Test run details** pane, select **Download**, and then select **Results**.
73
+
*Select **Download** on the **Test run details** pane. To download the results, select **Results**. To download the HTML report, select **Report**.
71
74
72
-
:::image type="content" source="media/how-to-export-test-results/dashboard-download.png" alt-text="Screenshot that shows how to download the test results from the 'Test run details' pane.":::
75
+
:::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.":::
73
76
74
-
1. You can use any zip tool to extract the folder and access the test results.
77
+
1. You can use any zip tool to extract the folder and access the downloaded files.
75
78
76
79
:::image type="content" source="media/how-to-export-test-results/test-results-zip.png" alt-text="Screenshot that shows the test results zip file in the downloads list.":::
77
80
78
-
The folder contains a separate CSV file for every test engine and contains details of requests that the test engine executed during the load test.
81
+
The results folder contains a separate CSV file for every test engine and contains details of requests that the test engine executed during the load test.
82
+
83
+
The report folder contains an HTML file that provides a summary of the test run and graphs of the performance metrics for offline viewing and collaboration.
79
84
80
85
# [GitHub Actions](#tab/github)
81
86
82
-
When you run a load test as part of your CI/CD pipeline, Azure Load Testing generates a test results file. Follow these steps to publish these test results and attach them to your CI/CD pipeline run:
87
+
When you run a load test as part of your CI/CD pipeline, Azure Load Testing generates test results and reports. Follow these steps to publish these test results and attach them to your CI/CD pipeline run:
83
88
84
89
1. Go to your GitHub repository, and select **Code**.
85
90
@@ -89,7 +94,7 @@ When you run a load test as part of your CI/CD pipeline, Azure Load Testing gene
89
94
90
95
1. Edit the workflow file and add the `actions/upload-artifact` action after the `azure/load-testing` action in the workflow file.
91
96
92
-
Azure Load Testing places the test results in the `loadTest` folder of the GitHub Actions workspace.
97
+
Azure Load Testing places the test results and the HTML report in the `loadTest` folder of the GitHub Actions workspace.
93
98
94
99
```yml
95
100
- name: 'Azure Load Testing'
@@ -105,7 +110,7 @@ When you run a load test as part of your CI/CD pipeline, Azure Load Testing gene
105
110
path: ${{ github.workspace }}/loadTest
106
111
```
107
112
108
-
1. After your GitHub Actions workflow completes, you can select the test results from the **Artifacts** section on the **Summary** page of the workflow run.
113
+
1. After your GitHub Actions workflow completes, you can select the **loadTestResults** folder from the **Artifacts** section on the **Summary** page of the workflow run.
109
114
110
115
:::image type="content" source="./media/how-to-export-test-results/github-actions-run-summary.png" alt-text="Screenshot that shows the GitHub Actions workflow summary page, highlighting the test results in the Artifacts section." lightbox="./media/how-to-export-test-results/github-actions-run-summary.png":::
111
116
@@ -119,7 +124,7 @@ When you run a load test as part of your CI/CD pipeline, Azure Load Testing gene
119
124
120
125
1. Edit the workflow file and add the `publish` task after the `AzureLoadTest` task in the workflow file.
121
126
122
-
Azure Load Testing places the test results in the `loadTest` folder of the Azure Pipelines default working directory.
127
+
Azure Load Testing places the test results and the HTML report in the `loadTest` folder of the Azure Pipelines default working directory.
123
128
124
129
```yml
125
130
- task: AzureLoadTest@1
@@ -134,7 +139,7 @@ When you run a load test as part of your CI/CD pipeline, Azure Load Testing gene
134
139
```
135
140
1. After your Azure Pipelines workflow completes, you can select the test results from the **Stages** section on the **Summary** page of the workflow run.
136
141
137
-
You can find and download the test results in the **Results** folder.
142
+
You can find and download the test results and the report in the **Results** folder.
138
143
139
144
:::image type="content" source="./media/how-to-export-test-results/azure-pipelines-run-summary.png" alt-text="Screenshot that shows the Azure Pipelines workflow summary page, highlighting the test results in the Stages section." lightbox="./media/how-to-export-test-results/azure-pipelines-run-summary.png":::
0 commit comments