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/tutorial-cicd-azure-pipelines.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -209,15 +209,13 @@ You'll create a new Azure pipeline that is linked to your fork of the sample app
209
209
210
210
To create and run the load test, the Azure Pipelines definition uses the [Azure Load Testing task](/azure/devops/pipelines/tasks/test/azure-load-testing) extension from the Azure DevOps Marketplace.
211
211
212
-
1. Install the **Azure Load Testing** task extension from the Azure DevOps Marketplace.
212
+
1. Open the [Azure Load Testing task extension](https://marketplace.visualstudio.com/items?itemName=AzloadTest.AzloadTesting) in the Azure DevOps Marketplace, and select **Get it free**.
213
213
214
-
:::image type="content" source="./media/tutorial-cicd-azure-pipelines/browse-marketplace.png" alt-text="Screenshot that shows how to browse the Visual Studio Marketplace for extensions.":::
215
-
216
-
:::image type="content" source="./media/tutorial-cicd-azure-pipelines/marketplace-load-testing-extension.png" alt-text="Screenshot that shows the button for installing the Azure Load Testing extension from the Visual Studio Marketplace.":::
214
+
1. Select your Azure DevOps organization, and then select **Install** to install the extension.
217
215
218
-
1. In your Azure DevOps project, select **Pipelines**, and then select **Create pipeline**.
216
+
If you don't have administrator privileges for the selected Azure DevOps organization, select **Request** to request an administrator to install the extension.
219
217
220
-
:::image type="content" source="./media/tutorial-cicd-azure-pipelines/create-pipeline.png" alt-text="Screenshot that shows selections for creating an Azure pipeline.":::
218
+
1. In your Azure DevOps project, select **Pipelines** in the left navigation, and then select **Create pipeline**.
221
219
222
220
1. On the **Connect** tab, select **GitHub**.
223
221
@@ -231,7 +229,7 @@ To create and run the load test, the Azure Pipelines definition uses the [Azure
231
229
232
230
1. Notice that the pipeline definition contains the `LoadTest` stage, which has two tasks.
233
231
234
-
The first task deploys a new Azure load testing resource using the `AzureResourceManagerTemplateDeployment` task.
232
+
The `AzureResourceManagerTemplateDeployment` task deploys a new Azure load testing resource in your Azure subscription.
235
233
236
234
Next, the `AzureLoadTest` [Azure Load Testing task](/azure/devops/pipelines/tasks/test/azure-load-testing) creates and starts a load test. This task uses the `SampleApp.yaml` [load test configuration file](./reference-test-config-yaml.md), which contains the configuration parameters for the load test, such as the number of parallel test engines.
237
235
@@ -251,17 +249,19 @@ To create and run the load test, the Azure Pipelines definition uses the [Azure
251
249
]
252
250
```
253
251
254
-
1. On the **Review** tab, replace the following placeholder text in the YAML code:
252
+
If a load test already exists, the `AzureLoadTest` task won't create a new load test, but will add a test run to this load test. To identify regressions over time, you can then [compare multiple test runs](./how-to-compare-multiple-test-runs.md).
253
+
254
+
1. On the **Review** tab, replace the following placeholder text at the beginning of the pipeline definition:
255
255
256
256
These variables are used to configure the deployment of the sample application, and to create the load test.
257
257
258
258
|Placeholder |Value |
259
259
|---------|---------|
260
-
|`<Name of your webapp>` | The name of the Azure App Service web app. |
260
+
|`<Name of your webapp>` | The name of the Azure App Service web app. |
261
261
| `<Name of your webARM Service connection>` | The name of the service connection that you created in the previous section. |
262
-
|`<Azure subscriptionId>` | Your Azure subscription ID. |
263
-
|`<Name of your load test resource>` | The name of your Azure Load Testing resource. |
264
-
|`<Name of your load test resource group>` | The name of the resource group that contains the Azure Load Testing resource. |
262
+
|`<Azure subscriptionId>` | Your Azure subscription ID. |
263
+
|`<Name of your load test resource>` | The name of your Azure Load Testing resource. |
264
+
|`<Name of your load test resource group>` | The name of the resource group that contains the Azure Load Testing resource. |
265
265
266
266
:::image type="content" source="./media/tutorial-cicd-azure-pipelines/create-pipeline-review.png" alt-text="Screenshot that shows the Azure Pipelines Review tab when you're creating a pipeline.":::
267
267
@@ -354,6 +354,7 @@ You can specify these criteria in the test configuration YAML file:
354
354
355
355
You've now created an Azure Pipelines CI/CD workflow that uses Azure Load Testing for automatically running load tests. By using pass/fail criteria, you can set the status of the CI/CD workflow. With parameters, you can make the running of load tests configurable.
356
356
357
+
* Learn more about [comparing results from multiple test runs](./how-to-compare-multiple-test-runs.md).
357
358
* Learn more about the [Azure Load Testing task](/azure/devops/pipelines/tasks/test/azure-load-testing).
358
359
* Learn more about [Parameterizing a load test](./how-to-parameterize-load-tests.md).
359
360
* Learn more [Define test pass/fail criteria](./how-to-define-test-criteria.md).
0 commit comments