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-testing-concepts.md
+27-25Lines changed: 27 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,11 +11,6 @@ ms.date: 11/03/2022
11
11
ms.custom: template-concept
12
12
---
13
13
14
-
<!--
15
-
Customer intent:
16
-
As a developer I want to understand the Azure Load Testing concepts so that I can set up a load test to identify performance issues in my application.
17
-
-->
18
-
19
14
# Key concepts for new Azure Load Testing Preview users
20
15
21
16
Learn about the key concepts and components of Azure Load Testing Preview. This can help you to more effectively set up a load test to identify performance issues in your application.
@@ -71,51 +66,58 @@ Learn about the key concepts and components of Azure Load Testing.
71
66
72
67
### Load testing resource
73
68
74
-
The Azure load testing resource is the top-level resource for your load-testing activities. This resource provides a centralized place to view and manage load tests, test results, and related artifacts. A load testing resource contains zero or more [load tests](#test).
69
+
The Azure load testing resource is the top-level resource for your load-testing activities. This resource provides a centralized place to view and manage load tests, test results, and related artifacts.
70
+
71
+
When you create a load test resource, you specify its location, which determines the location of the [test engines](#test-engine). Azure Load Testing automatically encrypts all artifacts in your resource. You can choose between Microsoft-managed keys or use your own customer-managed keys for encryption.
75
72
76
-
When you create a load test resource, you specify its location, which determines the location of the [test engines](#test-engine).
73
+
To run a load test for your application, you add a [test](#test) to your load testing resource. A resource can contain zero or more tests.
77
74
78
-
You can use [Azure role-based access control](./how-to-assign-roles.md)for granting access to your load testing resource.
75
+
You can use [Azure role-based access control](./how-to-assign-roles.md)to grant access to your load testing resource and related artifacts.
79
76
80
-
Azure Load Testing can use Azure Key Vault for [storing secret parameters](./how-to-parameterize-load-tests.md). You can [use either a user-assigned or system-assigned managed identity](./how-to-use-a-managed-identity.md) for your load testing resource.
77
+
Azure Load Testing lets you [use managed identities](./how-to-use-a-managed-identity.md) to access other Azure resources, such as Azure Key Vault for storing [load test secret parameters](./how-to-parameterize-load-tests.md). You can use either a user-assigned or system-assigned managed identity.
81
78
82
79
### Test
83
80
84
-
A test specifies the test script, and configuration settings for running a load test. You can create one or more tests in an Azure Load Testing resource.
81
+
A test represents a load test for your application. A test is attached to an Azure load testing resource. You can create a test in either of two ways:
82
+
83
+
- Create a [test based on an existing JMeter script](./how-to-create-and-run-load-test-with-jmeter-script.md).
84
+
- Create a [URL-based load test](./quickstart-create-and-run-load-test.md) (quick test). Azure Load Testing generates a corresponding JMeter script.
85
+
86
+
A test contains a JMeter test script, or *test plan*, and related data and configuration files. The test also specifies the configuration settings for running the load test:
85
87
86
-
The configuration of a load test consists of:
88
+
-[Load test parameters](./how-to-parameterize-load-tests.md), such as environment variables, secrets, and certificates.
89
+
- Load configuration to [scale out your load test](./how-to-high-scale-load.md) across multiple [test engine](#test-engine) instances.
90
+
-[Fail criteria](./how-to-define-test-criteria.md) to determine when the test should pass or fail.
91
+
- Monitoring settings to configure the list of [Azure app components and resource metrics to monitor](./how-to-monitor-server-side-metrics.md) during the test run.
87
92
88
-
- The test name and description.
89
-
- The Apache JMeter test script and related data and configuration files. For example, a [CSV data file](./how-to-read-csv-data.md).
- The number of [test engines](#test-engine) to run the test script on.
93
-
- The [fail criteria](./how-to-define-test-criteria.md) for the test.
94
-
- The list of [app components and resource metrics to monitor](./how-to-monitor-server-side-metrics.md) during the test execution.
93
+
When you start a test, Azure Load Testing deploys the JMeter test script, related files, and configuration to the requested test engine instances. The test engine instances then intiate the JMeter test script to simulate the application load.
95
94
96
-
When you run a test, a [test run](#test-run)instance is created.
95
+
Each time you start a test, Azure Load Testing creates a [test run](#test-run)and attaches it to the test.
97
96
98
97
### Test engine
99
98
100
-
A test engine is computing infrastructure, managed by Microsoft that runs the Apache JMeter test script. You can [scale out your load test](./how-to-high-scale-load.md) by configuring the number of test engines. The test script runs in parallel across the specified number of test engines.
99
+
A test engine is computing infrastructure, managed by Microsoft that runs the Apache JMeter test script. The test engine instances run the JMeter script in parallel. You can [scale out your load test](./how-to-high-scale-load.md) by configuring the number of test engine instances. Learn how to configure the number of [virtual users](#virtual-users), or simulate a target number of [requests per second](#requests-per-second-rps).
101
100
102
-
The test engines are hosted in the same location as your Azure Load Testing resource.
101
+
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.
103
102
104
-
While the test script runs, Azure Load Testing collects and aggregates the Apache JMeter worker logs. You can [download the logs for analyzing errors during the load test](./how-to-find-download-logs.md).
103
+
While the test script runs, Azure Load Testing collects and aggregates the Apache JMeter worker logs from all test engine instances. You can [download the logs for analyzing errors during the load test](./how-to-find-download-logs.md).
105
104
106
105
### Test run
107
106
108
107
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](./reference-test-config-yaml.md), the list of [app components to monitor](./how-to-monitor-server-side-metrics.md), and the [results of the test](./how-to-export-test-results.md).
109
108
110
-
During a test run, Azure Load Testing sends the Apache JMeter script to the specified number of [test engines](#test-engine). After the test run, the logs and test results are aggregated and collected from the test engines.
111
-
112
109
You can [view and analyze the load test results in the Azure Load Testing dashboard](./tutorial-identify-bottlenecks-azure-portal.md) in the Azure portal.
113
110
111
+
> [!IMPORTANT]
112
+
> Existing test runs don't use the new settings when you update a test. When you rerun an existing test run, the initial configuration of the test run is used. The new settings will only be used when you run the test.
113
+
114
114
### App component
115
115
116
116
When you run a load test for an Azure-hosted application, you can monitor resource metrics for the different Azure application components (server-side metrics). While the load test runs, and after completion of the test, you can [monitor and analyze the resource metrics in the Azure Load Testing dashboard](./how-to-monitor-server-side-metrics.md).
117
117
118
-
When you create or update a load test, you can configure the list of app components that Azure Load Testing will monitor. You can modify the list of default resource metrics for each app component. Learn more about which [Azure resource types are supported by Azure Load Testing](./resource-supported-azure-resource-types.md).
118
+
When you create or update a load test, you can configure the list of app components that Azure Load Testing will monitor. You can modify the list of default resource metrics for each app component.
119
+
120
+
Learn more about which [Azure resource types are supported by Azure Load Testing](./resource-supported-azure-resource-types.md).
0 commit comments