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/concept-load-test-app-service.md
+23-11Lines changed: 23 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,21 +101,33 @@ App Service diagnostics enables you to view in-depth information and dashboard a
101
101
102
102
## Parameterize your test for deployment slots
103
103
104
-
- Requires a JMeter script
105
-
- Deployment slots -> different endpoint
106
-
- Avoid hard-coding
107
-
- Use env vars to pass deployment slot and make URL configurable in JMeter script
108
-
- Also use for other configuration parameters (for example, number of virtual users, ramp-up time, and so on.)
104
+
[Azure App Service deployment slots](/azure/app-service/deploy-staging-slots) enable you to set up staging environments for your application. Each deployment slot has a separate URL. You can easily reuse your load testing script across multiple slots by using environment variables in the load test configuration.
109
105
110
-
## Authenticated endpoints
106
+
When you create a quick test, Azure Load Testing generates a generic JMeter script and uses environment variables to pass the target URL to the script.
111
107
112
-
- Use shared secrets or certificates
113
-
- Pass secrets into the JMeter script (store in Azure Key Vault or in CI/CD secrets store)
114
-
-[Azure AD authentication config](/azure/app-service/configure-authentication-provider-aad)
:::image type="content" source="media/concept-load-test-app-service/quick-test-parameters.png" alt-text="Screenshot that shows the Parameters page of a quick test in the Azure portal, highlighting the parameters for the target URL." lightbox="media/concept-load-test-app-service/quick-test-parameters.png":::
109
+
110
+
To use environment variables for passing the deployment slot URL to your JMeter test script, perform the following steps:
111
+
112
+
1. Add an environment variable in the load test configuration.
113
+
114
+
1. Reference the environment variable in your test script by using the `System.getenv` function.
Learn how to [parameterize a load test by using environment variables](./how-to-parameterize-load-tests.md).
125
+
126
+
You can also use environment variables to pass other configuration settings to the JMeter test script. For example, you might pass the number of virtual users, or the file name of a [CSV input file](./how-to-read-csv-data.md) to the test script.
116
127
117
128
## Next steps
118
129
130
+
- Get started by [creating a URL-based load test](./quickstart-create-and-run-load-test.md).
131
+
- Learn how to [identify performance bottlenecks](./tutorial-identify-bottlenecks-azure-portal.md) for Azure applications.
119
132
- Learn how to [configure your test for high-scale load](./how-to-high-scale-load.md).
120
133
- Learn how to [configure automated performance testing](./tutorial-identify-performance-regression-with-cicd.md).
121
-
- Learn how to [identify performance bottlenecks](./tutorial-identify-bottlenecks-azure-portal.md) for Azure applications.
0 commit comments