Merge pull request #292819 from saloniagrawal1997/JMXFragments

Jmx fragments

Author: JillGrant615

articles/load-testing/how-to-create-and-run-load-test-with-jmeter-script.md

@@ -14,7 +14,7 @@ adobe-target: true
 
 # Load test a website by using a JMeter script in Azure Load Testing
 
-Learn how to use an Apache JMeter script to load test a web application with Azure Load Testing from the Azure portal or by using the Azure CLI. Azure Load Testing enables you to take an existing Apache JMeter script, and use it to run a load test at cloud scale. Learn more about which [JMeter functionality that Azure Load Testing supports](./resource-jmeter-support.md).
+Learn how to use an Apache JMeter script to load test a web application with Azure Load Testing from the Azure portal or by using the Azure CLI. Azure Load Testing enables you to take existing Apache JMeter scripts, and use it to run a load test at cloud scale. Learn more about which [JMeter functionality that Azure Load Testing supports](./resource-jmeter-support.md).
 
 Use cases for creating a load test with an existing JMeter script include:
 
@@ -40,7 +40,7 @@ To create a load testing resource:
 
 ## Create a load test
 
-Next, you create a load test by uploading an Apache JMeter test script (JMX file). The test script contains the application requests to simulate traffic to your application endpoints.
+Next, you create a load test by uploading Apache JMeter test scripts (JMX files). The test script contains the application requests to simulate traffic to your application endpoints.
 
 # [Azure portal](#tab/portal)
 
@@ -62,12 +62,12 @@ To create a load test using an existing JMeter script in the Azure portal:
     | **Test description**         | (Optional) Enter a load test description. |
     | **Run test after creation**  | Select this setting to automatically start the load test after saving it. |
 
-1. On the **Test plan** tab, select your Apache JMeter script, and then select **Upload** to upload the file to Azure.
+1. On the **Test plan** tab, select your Apache JMeter scripts, and then select **Upload** to upload the files to Azure. In case you have multiple JMeter scripts, specify the main test script from which the execution should begin in File relevance.
 
     :::image type="content" source="./media/how-to-create-and-run-load-test-with-jmeter-script/create-new-test-test-plan.png" alt-text="Screenshot that shows the Test plan tab." lightbox="./media/how-to-create-and-run-load-test-with-jmeter-script/create-new-test-test-plan.png":::
 
     > [!NOTE]
-    > You can upload additional JMeter configuration files or other files that you reference in the JMX file. For example, if your test script uses CSV data sets, you can upload the corresponding *.csv* file(s). See also how to [read data from a CSV file](./how-to-read-csv-data.md). For files other than JMeter scripts and user properties, if the size of the file is greater than 50 MB, zip the file. The size of the zip file should be below 50 MB. Azure Load Testing automatically unzips the file during the test run. Only five zip artifacts are allowed with a maximum of 1000 files in each zip and an uncompressed total size of 1 GB.
+    > You can upload additional JMeter configuration files or other files that you reference in the JMX file. For example, if your test script uses CSV data sets, you can upload the corresponding *.csv* file(s). See also how to [read data from a CSV file](./how-to-read-csv-data.md). For files other than the main test script and user properties, if the size of the file is greater than 50 MB, zip the file. The size of the zip file should be below 50 MB. Azure Load Testing automatically unzips the file during the test run. Only five zip artifacts are allowed with a maximum of 1000 files in each zip and an uncompressed total size of 1 GB.
 
 1. Select **Review + create**. Review all settings, and then select **Create** to create the load test.
 

articles/load-testing/media/how-to-create-and-run-load-test-with-jmeter-script/create-new-test-test-plan.png

@@ -29,11 +29,11 @@ A load test configuration uses the following keys:
 | `testType` | string | Y | | Test type. Possible values:<br/><ul><li>`URL`: URL-based load test</li><li>`JMX`: JMeter-based load test</li><li>`Locust`: Locust-based load test</li></ul> |
 | `testPlan` | string | Y |  | Reference to the test plan file.<br/><ul><li>If `testType: JMX`: relative path to the JMeter test script.</li><li>If `testType: Locust`: relative path to the Locust test script.</li><li>If `testType: URL`: relative path to the [requests JSON file](./how-to-add-requests-to-url-based-test.md).</li></ul> |
 | `engineInstances` | integer | Y |  | Number of parallel test engine instances for running the test plan. Learn more about [configuring high-scale load](./how-to-high-scale-load.md). |
-| `configurationFiles` | array of string | N |  | List of external files, required by the test script. For example, CSV data files, images, or any other data file.<br/>Azure Load Testing uploads all files in the same folder as the test script. In the JMeter script or the Locust script, only refer to external files using the file name, and remove any file path information. |
+| `configurationFiles` | array of string | N |  | List of external files, required by the test script. For example, JMX fragment files, CSV data files, images, or any other data file.<br/>Azure Load Testing uploads all files in the same folder as the test script. In the JMeter script or the Locust script, only refer to external files using the file name, and remove any file path information. |
 | `failureCriteria` | object | N |  | List of load test fail criteria. See [failureCriteria](#failurecriteria-configuration) for more details. |
 | `autoStop` | string or object | N |  | Automatically stop the load test when the error percentage exceeds a value.<br/>Possible values:<br/>- `disable`: don't stop a load test automatically.<br/>- *object*: see [autostop](#autostop-configuration) configuration for more details. |
 | `properties` | object | N |  | <ul><li>If `testType: JMX`: JMeter user property file references.</li><li>If `testType: Locust`: Locust configuration file references.</li></ul> See [properties](#properties-configuration) for more details. |
-| `zipArtifacts` | array of string| N |  | Specifies the list of zip artifact files. For files other than JMeter scripts and user properties for JMeter-based tests and Locust script and configuration files for Locust-based tests, if the file size exceeds 50 MB, compress them into a ZIP file. Ensure that the ZIP file remains below 50 MB in size. Only 5 ZIP artifacts are allowed with a maximum of 1000 files in each and uncompressed size of 1 GB. Only applies for `testType: JMX` and `testType: Locust`. |
+| `zipArtifacts` | array of string| N |  | Specifies the list of zip artifact files. For files other than the main JMeter script and user properties for JMeter-based tests and Locust script and configuration files for Locust-based tests, if the file size exceeds 50 MB, compress them into a ZIP file. Ensure that the ZIP file remains below 50 MB in size. Only 5 ZIP artifacts are allowed with a maximum of 1000 files in each and uncompressed size of 1 GB. Only applies for `testType: JMX` and `testType: Locust`. |
 | `splitAllCSVs` | boolean | N | False | Split the input CSV files evenly across all test engine instances. For more information, see [Read a CSV file in load tests](./how-to-read-csv-data.md#split-csv-input-data-across-test-engines). |
 | `secrets` | object | N |  | List of secrets that the Apache JMeter or Locust script references. See [secrets](#secrets-configuration) for more details. |
 | `env` | object | N |  | List of environment variables that the Apache JMeter script or Locust references. See [environment variables](#env-configuration) for more details. |
@@ -58,6 +58,7 @@ engineInstances: 1
 subnetId: /subscriptions/abcdef01-2345-6789-0abc-def012345678/resourceGroups/sample-rg/providers/Microsoft.Network/virtualNetworks/load-testing-vnet/subnets/load-testing
 configurationFiles:
   - 'sampledata.csv'
+  - ‘testfragment.jmx’
 zipArtifacts:
    - bigdata.zip
 splitAllCSVs: True

articles/load-testing/media/how-to-create-and-run-load-test-with-jmeter-script/create-new-test.png

@@ -12,7 +12,7 @@ ms.date: 06/14/2023
 
 # Supported Apache JMeter features in Azure Load Testing
 
-Azure Load Testing enables you to use an existing Apache JMeter script (JMX) to create and run a load test. This article explains which Apache JMeter features are supported in Azure Load Testing.
+Azure Load Testing enables you to use existing Apache JMeter scripts (JMX) to create and run a load test. This article explains which Apache JMeter features are supported in Azure Load Testing.
 
 See the Azure Load Testing overview to learn [how Azure Load Testing works](./overview-what-is-azure-load-testing.md#how-does-azure-load-testing-work).
 
@@ -28,15 +28,15 @@ The following table lists the Apache JMeter features and their support in Azure
 | ------- | ------- | ---------------- |
 | Test plan elements | - Thread groups<br/>- Variables<br/>- Functions<br/>- Samplers<br/>- Logic controllers<br/>- Timers<br/>- Assertions<br/>- Preprocessors<br/>- Postprocessors | [Create a load test by using a JMeter script](./how-to-create-and-run-load-test-with-jmeter-script.md) |
 | Samplers | All samplers and protocols are supported. | [Create a load test with a JMeter script](./how-to-create-and-run-load-test-with-jmeter-script.md) |
-| Controllers | All logic controllers are supported, except for [Include controller](https://jmeter.apache.org/usermanual/component_reference.html#Include_Controller), [Module controller](https://jmeter.apache.org/usermanual/component_reference.html#Module_Controller), and [Recording controller](https://jmeter.apache.org/usermanual/component_reference.html#Recording_Controller). | [Create a load test with a JMeter script](./how-to-create-and-run-load-test-with-jmeter-script.md) |
+| Controllers | All logic controllers are supported, except for [Recording controller](https://jmeter.apache.org/usermanual/component_reference.html#Recording_Controller). | [Create a load test with a JMeter script](./how-to-create-and-run-load-test-with-jmeter-script.md) |
 | Scripting | - BeanShell<br/>- JSR223 script | |
 | Configuration elements | All configuration elements are supported.  | Example: [Read data from a CSV file](./how-to-read-csv-data.md) |
 | JMeter properties | Azure Load Testing supports uploading a single user properties file per load test to override JMeter configuration settings or add custom properties.<br/>System properties files aren't supported. | [Configure JMeter user properties](./how-to-configure-user-properties.md) |
 | Plugins | Azure Load Testing lets you use plugins from https://jmeter-plugins.org, or upload a Java archive (JAR) file with your own plugin code.| [Customize a load test with plugins](./how-to-use-jmeter-plugins.md) |
 | Web Driver sampler | Due to the resource intensive nature of WebDriver tests, you can run tests with a load of up to four virtual users associated with the [Web Driver sampler](https://jmeter-plugins.org/wiki/WebDriverSampler/). Tests with higher load associated with the Web Driver sampler can result in errors. In such a case, reduce the load and try again.<br/>You can have a higher load associated with other samplers, like HTTP sampler, in the same test.  | |
 | Listeners | Azure Load Testing ignores all [Results Collectors](https://jmeter.apache.org/api/org/apache/jmeter/reporters/ResultCollector.html), which includes visualizers such as the [results tree](https://jmeter.apache.org/usermanual/component_reference.html#View_Results_Tree) or [graph results](https://jmeter.apache.org/usermanual/component_reference.html#Graph_Results). | |
 | Dashboard report | The Azure Load Testing dashboard shows the client metrics, and optionally the server-side metrics. <br/>You can export the load test results to use them in a reporting tool or [generate the JMeter dashboard](https://jmeter.apache.org/usermanual/generating-dashboard.html#report) on your local machine.| [Export test results](./how-to-export-test-results.md) | 
-| Test fragments| Not supported. | |
+| Test fragments| Test fragments are supported. | |
 
 ## Next steps