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-parameterize-load-tests.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,7 +164,7 @@ You've now specified a secret in the CI/CD secret store and passed a reference t
164
164
165
165
Next, you update the test script to use the secret that you specified earlier.
166
166
167
-
# [Apache JMeter](#tab/jmeter)
167
+
## [Apache JMeter](#tab/jmeter)
168
168
169
169
You first create a user-defined variable that retrieves the secret value. Then, you can use this variable in your test (for example, to pass an API token in an HTTP request header).
170
170
@@ -206,7 +206,7 @@ You first create a user-defined variable that retrieves the secret value. Then,
206
206
</HeaderManager>
207
207
```
208
208
209
-
# [Locust](#tab/locust)
209
+
## [Locust](#tab/locust)
210
210
211
211
The secrets configured in the load test configuration are accessible as environment variables.
212
212
@@ -233,7 +233,7 @@ In this section, you update the Apache JMeter script to use environment variable
233
233
234
234
You first define a user-defined variable that reads the environment variable, and then you can use this variable in the test execution (for example, to update the HTTP domain).
235
235
236
-
# [Apache JMeter](#tab/jmeter)
236
+
## [Apache JMeter](#tab/jmeter)
237
237
238
238
1. Create a user-defined variable in your JMX file, and assign the environment variable's value to it by using the `System.getenv` function.
239
239
@@ -266,7 +266,7 @@ You first define a user-defined variable that reads the environment variable, an
0 commit comments