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: sdk/loadtestservice/Azure.Developer.LoadTesting/CHANGELOG.md
+13-6Lines changed: 13 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,21 @@
1
1
# Release History
2
2
3
-
## 1.1.0-beta.1 (Unreleased)
3
+
## 1.2.0-beta.1 (2025-04-15)
4
4
5
5
### Features Added
6
6
7
-
### Breaking Changes
8
-
9
-
### Bugs Fixed
10
-
11
-
### Other Changes
7
+
- Added capabilities to support all changes present in Azure Load Testing API Version 2024-05-01-preview
8
+
- This release adds all the models for all the APIs supported by Azure Load Testing. Relevant new client method overloads are also added to work with these new methods
9
+
- Added support for the following features:
10
+
- Support for specifying AutoStopCriteria for LoadTests
11
+
- Support for Quick Load Tests with `RequestsPerSecond` input
12
+
- Support for URL Tests with JSON Based Test Plans and Locust Tests using the `TestKind` field
13
+
- Support for multi region load tests to generate load from multiple regions
14
+
- Support for disabling Public IP Deployment for Private Load Tests using the `publicIpDisabled` field
15
+
- Support for uploading Zipped Artifacts as test input artifacts
16
+
- Added Client Methods to work with `TestProfiles` and `TestProfileRuns`
17
+
- Added methods `CreateOrUpdateTestProfile`, `GetTestProfile`, `DeleteTestProfile` and `GetTestProfiles` along with their async variants to work with test profiles
18
+
- Added methods `BeginTestProfileRun`, `GetTestProfileRun`, `DeleteTestProfileRun` and `GetTestProfileRuns` along with their async variants to work with test profile runs
Copy file name to clipboardExpand all lines: sdk/loadtestservice/Azure.Developer.LoadTesting/README.md
+55-30Lines changed: 55 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,30 +1,31 @@
1
1
# Azure Load Testing client library for .NET
2
+
2
3
Azure Load Testing provides client library in .NET to the user by which they can interact natively with Azure Load Testing service. Azure Load Testing is a fully managed load-testing service that enables you to generate high-scale load. The service simulates traffic for your applications, regardless of where they're hosted. Developers, testers, and quality assurance (QA) engineers can use it to optimize application performance, scalability, or capacity.
Install the client library for .NET with [NuGet](https://www.nuget.org/):
20
+
Install the client library for .NET with [NuGet](https://www.nuget.org/):
21
21
22
22
```dotnetcli
23
23
dotnet add package Azure.Developer.LoadTesting
24
24
```
25
25
26
26
### Prerequisites
27
-
You must have an [Azure subscription](https://azure.microsoft.com/free/dotnet/) and [Azure Load Test Service Resource](https://learn.microsoft.com/azure/load-testing/). In order to take advantage of the C# 8.0 syntax, it is recommended that you compile using the [.NET Core SDK](https://dotnet.microsoft.com/download) 3.0 or higher with a [language version](https://learn.microsoft.com/dotnet/csharp/language-reference/configure-language-version#override-a-default) of `latest`. It is also possible to compile with the .NET Core SDK 2.1.x using a language version of `preview`.
27
+
28
+
You must have an [Azure subscription](https://azure.microsoft.com/free/dotnet/) and [Azure Load Test Service Resource](https://learn.microsoft.com/azure/load-testing/) to use this package. You can create the resource via the [Azure Portal](https://portal.azure.com), or the [Azure CLI](https://learn.microsoft.com/cli/azure).
28
29
29
30
30
31
### Authenticate the client
@@ -49,7 +50,7 @@ The following components make up the Azure Load Testing service. The Azure Load
49
50
50
51
-`LoadTestRunClient`
51
52
52
-
These clients are used for managing and using different components of the service. For each method in both of these sub-clients there is a corresponding Async method in the same class, with the same implementation however enabling async functionalities. For example, if there is a method, `CreateOrUpdateTest` as a part of `LoadTestAdministrationClient` then there always exists one more function`CreateOrUpdateTestAsync` in the same client class.
53
+
These clients are used for managing and using different components of the service. For each method in both of these sub-clients there is a corresponding Async method in the same class, with the same implementation however enabling async functionalities. For example, if there is a method, `CreateOrUpdateTest` as a part of `LoadTestAdministrationClient` then there always exists one more method`CreateOrUpdateTestAsync` in the same client class.
53
54
54
55
### Load Test Administration Client
55
56
@@ -73,7 +74,7 @@ During a load test, Azure Load Testing collects metrics about the test execution
73
74
74
75
### Test Run Client
75
76
76
-
The `LoadTestRunClient` client is used to start and stop test runs corresponding to a load test. A test run represents one execution of a load test. It collects the logs associated with running the Apache JMeter script, the load test YAML configuration, the list of app components to monitor, and the results of the test.
77
+
The `LoadTestRunClient` client is used to start and stop test runs corresponding to a load test. A test run represents one execution of a load test. It collects the logs associated with running the test script, the load test configuration, the list of app components to monitor, and the results of the test.
77
78
78
79
### Data-Plane Endpoint
79
80
@@ -83,50 +84,72 @@ Data-plane of Azure Load Testing resources is addressable using the following UR
83
84
84
85
The first GUID `00000000-0000-0000-0000-000000000000` is the unique identifier used for accessing the Azure Load Testing resource. This is followed by `aaa` which is the Azure region of the resource.
85
86
86
-
The data-plane endpoint is obtained from Control Plane APIs.
87
+
The data-plane endpoint is obtained from Control Plane APIs. To obtain the data-plane endpoint for your resource, follow [this documentation][obtaining_data_plane_uri].
In the above example, `eastus` represents the Azure region `East US`.
92
+
93
+
### Thread Safety
94
+
95
+
We guarantee that all client instance methods are thread-safe and independent of each other ([guideline](https://azure.github.io/azure-sdk/dotnet_introduction.html#dotnet-service-methods-thread-safety)). This ensures that the recommendation of reusing client instances is always safe, even across threads.
[Accessing the response](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/core/Azure.Core/README.md#accessing-http-response-details-using-responset) |
In the above example, `eus` represents the Azure region `East US`.
91
109
## Examples
92
110
93
111
You can familiarize yourself with different APIs using [Samples](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/loadtestservice/Azure.Developer.LoadTesting/samples).
94
112
95
-
96
113
## Troubleshooting
97
-
More about it is coming soon...
98
114
115
+
### Setting up console logging
99
116
100
-
### Thread safety
117
+
The simplest way to see the logs is to enable the console logging. To create an Azure SDK log listener that outputs messages to the console, use `AzureEventSourceListener.CreateConsoleLogger` method.
101
118
102
-
We guarantee that all client instance methods are thread-safe and independent of each other ([guideline](https://azure.github.io/azure-sdk/dotnet_introduction.html#dotnet-service-methods-thread-safety)). This ensures that the recommendation of reusing client instances is always safe, even across threads.
To learn more about other logging mechanisms see [here][azure_core_diagnostics].
103
125
104
126
## Next steps
105
127
106
-
Get started with our [samples](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/loadtestservice/Azure.Developer.LoadTesting/samples).
128
+
For more extensive documentation on Azure Load Testing, see the [Azure Load Testing documentation][product_documentation].
129
+
130
+
Get started with our [samples](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/loadtestservice/Azure.Developer.LoadTesting/samples) that cover common scenarios.
107
131
108
132
## Contributing
109
133
110
-
This is a template, but your SDK readme should include details on how to contribute code to the repo/package.
134
+
See the [CONTRIBUTING.md](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md) file for information about how to onboard and contribute to the overall Azure SDK ecosystem.
135
+
136
+
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit [cla.microsoft.com][cla].
137
+
138
+
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
139
+
140
+
This project has adopted the [Microsoft Open Source Code of Conduct][code_of_conduct]. For more information see the [Code of Conduct FAQ][code_of_conduct_faq] or contact [[email protected]][email_opencode] with any additional questions or comments.
[Accessing the response](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/core/Azure.Core/README.md#accessing-http-response-details-using-responset) |
0 commit comments