Skip to content

Commit c75cbb9

Browse files
Addressing PR review comments
1 parent c4b9bf5 commit c75cbb9

File tree

3 files changed

+17
-17
lines changed

3 files changed

+17
-17
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -124,6 +124,8 @@ 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.
128+
127129
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).
128130

129131
### App component

articles/load-testing/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ landingContent:
3636
url: how-to-create-and-run-load-test-with-JMeter-script.md
3737
- text: Create a load test with a Locust script
3838
url: quickstart-create-run-load-test-with-locust.md
39-
- text: Create and run a load test from Visual Studio Code
39+
- text: Create and run a load test with Visual Studio Code and GitHub Copilot
4040
url: quickstart-create-run-load-tests-from-visual-studio-code.md
4141
- text: Automate load tests with Azure Pipelines
4242
url: quickstart-add-load-test-cicd.md

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

Lines changed: 14 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: 'Quickstart: Create and run load tests from Visual Studio Code'
33
titleSuffix: Azure Load Testing
4-
description: 'This quickstart shows how to create and run load tests using the Visual Studio code extension for Azure Load Testing. Azure Load Testing is a managed, cloud-based load testing tool.'
4+
description: 'This quickstart shows how to create and run load tests using the Visual Studio Code extension for Azure Load Testing. Azure Load Testing is a managed, cloud-based load testing tool.'
55
services: load-testing
66
ms.service: azure-load-testing
77
ms.topic: quickstart
@@ -10,11 +10,11 @@ ms.author: vevippar
1010
ms.date: 04/04/2024
1111
---
1212

13-
# Quickstart: Create and run a load test from Visual Studio Code with Azure Load Testing
13+
# Quickstart: Create and run a load test with Visual Studio Code and GitHub Copilot
1414

1515
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.
1616

17-
This quickstart guides you through generating, refining, and running realistic load tests. By the end, you'll 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**.
17+
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

1919
:::image type="content" source="./media/quickstart-create-run-load-tests-from-visual-studio-code/create-locust-test.gif" alt-text="Image sequence that shows the creation of a Locust script using Azure Load Testing VS Code extension" lightbox="./media/quickstart-create-run-load-tests-from-visual-studio-code/create-locust-test.gif":::
2020

@@ -43,7 +43,7 @@ You can also access the features directly from the command palette by using the
4343

4444
## Generate a Locust script with Copilot
4545

46-
You can generate a Locust script from any existing Postman collection, Insomnia collection, or .http file. If the file contains multiple requests, Copilot will attempt to sequence them into a cohesive scenario.
46+
You can generate a Locust script from any existing Postman collection, Insomnia collection, or .http file. If the file contains multiple requests, Copilot attempts to sequence them into a cohesive scenario.
4747

4848
1. For this quickstart, download and save the [sample PetStore .http file](https://aka.ms/malt-vscode/http-sample) in your current VS Code workspace.
4949

@@ -59,9 +59,9 @@ You can generate a Locust script from any existing Postman collection, Insomnia
5959

6060
1. Select the sample file which you saved earlier to your workspace: [**`petstore-sample.http`**](https://aka.ms/malt-vscode/http-sample).
6161

62-
1. Copilot will analyze the selected file and generate a **Locust-based load test script**, automatically sequencing API requests to simulate real-world usage and handling authentication securely.
62+
1. Copilot analyzes the selected file and generate a **Locust-based load test script**, automatically sequencing API requests to simulate real-world usage and handling authentication securely.
6363

64-
1. Once the script is generated, the **Copilot Chat** window will suggest additional setup steps, such as defining **environment variables**. If Copilot suggests environment variables, create a `.env` file in your project and add the recommended values.
64+
1. Once the script is generated, the **Copilot Chat** window will suggest other setup steps, such as defining **environment variables**. If Copilot suggests environment variables, create a `.env` file in your project and add the recommended values.
6565

6666
## Customize the load test script
6767

@@ -82,12 +82,12 @@ To make the test more dynamic by randomizing the request payload:
8282

8383
1. Open the **Copilot Chat** panel.
8484
2. Type: `Randomize request payloads` and press Enter.
85-
3. Copilot will generate a suggested modification to introduce randomization.
85+
3. Copilot generates a suggested modification to introduce randomization.
8686
4. Click **Apply in Editor** that appears above the generated code snippet in Copilot Chat window.
8787
5. After reviewing the changes, click **Keep** to accept and update your script.
8888
6. Save the file
8989

90-
Now, each request simulates a more realistic user interaction. The code will look something like the following:
90+
Now, each request simulates a more realistic user interaction. The code looks something like the following snippet:
9191

9292
```python
9393
payload = {
@@ -111,9 +111,9 @@ To quickly validate your test, run it locally using Locust from **Visual Studio
111111

112112
1. Open the command palette and run: **Load Testing: Run load test (local)**.
113113

114-
1. This will automatically launch the **Locust web UI** in a browser. It can take a few seconds for the Locust server to be ready and for the browser to open.
114+
1. The **Locust web UI** gets automatically launched in a browser. It can take a few seconds for the Locust server to be ready and for the browser to open.
115115

116-
1. In the **Start new load test** page, review the input fields and click **Start**. Locust will begin sending requests, logging any failures, and tracking performance statistics.
116+
1. In the **Start new load test** page, review the input fields and click **Start**. Locust starts sending requests, logging any failures, and tracking performance statistics.
117117

118118
:::image type="content" source="./media/quickstart-create-run-load-tests-from-visual-studio-code/locust-start-new-load-test.png" alt-text="Screenshot that shows the Locust web UI to run a load test locally." lightbox="./media/quickstart-create-run-load-tests-from-visual-studio-code/locust-start-new-load-test.png":::
119119

@@ -135,7 +135,7 @@ If you prefer running the test from a **VS Code Terminal**:
135135
```
136136
* `-f path/to/locustfile.py`: Specifies the Locust test script.
137137
* `-u 10`: Simulates up to 10 virtual users.
138-
* `-r 2`: Ramps up 2 virtual users per second.
138+
* `-r 2`: Ramps up two virtual users per second.
139139
* `--run-time 1m`: Runs the test for 1 minute.
140140
1. Open a browser to `http://0.0.0.0:8089` to view the Locust web UI.
141141

@@ -156,8 +156,8 @@ To execute a large-scale test:
156156

157157
- Choosing load test regions to distribute traffic globally.
158158

159-
1. Once the setup is complete, a YAML configuration file (e.g., `loadtest.config.yaml`) is generated and added to your workspace root folder.
160-
- This file defines the Locust script, load parameters, environment variables, regions, and any additional files (e.g., CSV datasets).
159+
1. Once the setup is complete, a YAML configuration file (for example, `loadtest.config.yaml`) is generated and added to your workspace root folder.
160+
- This file defines the Locust script, load parameters, environment variables, regions, and any other files (for example, CSV datasets).
161161

162162
- Defaults are 200 virtual users running for 120 seconds in each selected region.
163163

@@ -172,10 +172,8 @@ To execute a large-scale test:
172172
> [!NOTE]
173173
> To quickly access test results from previous runs, use the command: **Load Testing: View load test runs**.
174174

175-
![Azure Load Testing report](media/run-load-test-azure.gif)
176175
:::image type="content" source="./media/quickstart-create-run-load-tests-from-visual-studio-code/run-load-test-azure.gif" alt-text="Image sequence that shows the test results dashboard in Azure Load Testing." lightbox="./media/quickstart-create-run-load-tests-from-visual-studio-code/run-load-test-azure.gif":::
177176

178-
179177
## Next Steps
180178

181179
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.
@@ -184,7 +182,7 @@ So far in this quickstart, sensitive variables like `API_KEY` were stored in a `
184182

185183
1. Open the **Copilot Chat** window, type `@testing /setupLoadTestSecretsInAzure` and hit Enter.
186184

187-
1. Copilot will guide you through:
185+
1. Copilot guides you through:
188186
- Creating an Azure Key Vault.
189187
- Assigning a managed identity to your Azure Load Testing resource.
190188
- Adding secrets to Azure Key Vault.

0 commit comments

Comments
 (0)