Skip to content

Commit f9e79d9

Browse files
Addressing PR review comments
1 parent dbcc10b commit f9e79d9

File tree

5 files changed

+9
-6
lines changed

5 files changed

+9
-6
lines changed

articles/load-testing/concept-load-testing-concepts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ A test engine is computing infrastructure, managed by Microsoft that runs the te
124124

125125
The test engines are hosted in the same location as your Azure Load Testing resource. You can configure the Azure region when you create the Azure load testing resource.
126126

127-
Azure Load Testing uses Standard_D4d_v4 size Virtual Machines with four vCPUs, 16GB Memory and Azure Linux operating system as the test engines. For JMeter based tests, the test engines use JDK 21 and Apache JMeter version 5.6.3. For Locust based tests, the test engines use Python 3.9.19 and Locust version 2.33.2.
127+
Azure Load Testing uses Standard_D4d_v4 size virtual machines with four vCPUs, 16GB memory and Azure Linux operating system as the test engines. For JMeter based tests, the test engines use JDK 21 and Apache JMeter version 5.6.3. For Locust based tests, the test engines use Python 3.9.19 and Locust version 2.33.2.
128128

129129
While the test script runs, Azure Load Testing collects and aggregates the testing framework logs from all test engine instances. You can [download the logs for analyzing errors during the load test](./how-to-diagnose-failing-load-test.md).
130130

15.3 KB
Loading
-144 KB
Loading
-1.76 KB
Loading

articles/load-testing/quickstart-create-run-load-tests-from-visual-studio-code.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.date: 04/04/2024
1212

1313
# Quickstart: Create and run a load test with Visual Studio Code and GitHub Copilot
1414

15-
Learn how to use the Azure Load Testing extension for Visual Studio Code to easily create Locust load tests using Copilot, iterate locally, and scale effortlessly in Azure. Whether you're new to Locust or a performance testing expert, the Azure Load Testing extension streamlines test creation, iteration, and scaling, right from your VS Code environment. Azure Load Testing is a managed service that lets you run a load test at cloud scale. [Locust](https://locust.io/) is an open source load testing tool that enables you to describe all your test in Python code.
15+
Learn how to use the Azure Load Testing extension for Visual Studio Code to easily create Locust load tests using Copilot, iterate locally, and scale effortlessly in Azure. Whether you're new to Locust or a performance testing expert, the Azure Load Testing extension streamlines test creation, iteration, and scaling, right from your VS Code environment. Azure Load Testing is a managed service that lets you run a load test at cloud scale. [Locust](https://locust.io/) is an open source load testing tool that enables you to write all your tests in Python code.
1616

1717
This quickstart guides you through generating, refining, and running realistic load tests. By the end, you have a fully functional load test script generated from a **Postman collection**, **Insomnia collection**, or **.http file**, enhanced with Copilot-powered improvements, and ready to scale in **Azure Load Testing**.
1818

@@ -162,9 +162,11 @@ To execute a large-scale test:
162162

163163
- Commit this file in your repository to reuse and automate future load test executions.
164164

165-
1. Copilot validates the configuration before execution. Follow any instructions provided in the chat window. Otherwise, if everything checks out, the test script and its related artifacts are uploaded to Azure Load Testing and prepared for execution. This process may take up to a minute, progress is shown in the **Output** panel.
165+
1. Copilot validates the configuration before execution. Follow any instructions provided in the chat window. Otherwise, if everything checks out, the test script and its related artifacts are uploaded to Azure Load Testing and prepared for execution. This process may take up to a minute, and progress is shown in the **Output** panel.
166+
166167

167168
:::image type="content" source="./media/quickstart-create-run-load-tests-from-visual-studio-code/load-test-progress.png" alt-text="Screenshot that shows the load test progress in VS Code output console." lightbox="./media/quickstart-create-run-load-tests-from-visual-studio-code/load-test-progress.png":::
169+
1. When the test starts, a notification (toast message) appears in the bottom-right corner of VS Code. Click the **Open in Azure Portal** button to monitor test execution in real time.
168170

169171
1. When the test starts, a notification (toast message) appears in the bottom-right corner. Click the **Open in Azure Portal** button to monitor test execution in real time.
170172

@@ -173,13 +175,14 @@ To execute a large-scale test:
173175
> [!TIP]
174176
> To quickly access test results from previous runs, use the command: **Load Testing: View load test runs**.
175177

176-
## Next Steps
178+
In this quickstart, sensitive variables like `API_KEY` were stored in a `.env` file and uploaded to the cloud service. However, as a best practice, secrets should be securely managed in **Azure Key Vault**. The extension provides guidance on setting this up.
177179

178180
So far in this quickstart, sensitive variables like `API_KEY` were stored in a `.env` file and uploaded to the cloud service. However, as a best practice, secrets should be securely managed in **Azure Key Vault**. The extension provides guidance on setting this up.
179181

180-
### Secure Secrets with Azure Key Vault
182+
1. Open the **Copilot Chat** window, type `@testing /setupLoadTestSecretsInAzure` and press Enter.
183+
184+
1. Copilot guides you through the following steps:
181185

182-
1. Open the **Copilot Chat** window, type `@testing /setupLoadTestSecretsInAzure` and hit Enter.
183186

184187
1. Copilot guides you through:
185188
- Creating an Azure Key Vault.

0 commit comments

Comments
 (0)