Add AzureEngine to ease execution of test plans in Azure Load Testing

Additionally, refactor octoperf and blazemeter engines to reuse logic and avoid duplication.

Author: rabelenda-abstracta

.github/workflows/build.yml

@@ -21,3 +21,4 @@ jobs:
         env:
           BZ_TOKEN: ${{ secrets.BZ_TOKEN }}
           OCTOPERF_API_KEY: ${{ secrets.OCTOPERF_API_KEY }}
+          AZURE_CREDS: ${{ secrets.AZURE_CREDS }}

.github/workflows/release.yml

@@ -43,6 +43,7 @@ jobs:
         env:
           BZ_TOKEN: ${{ secrets.BZ_TOKEN }}
           OCTOPERF_API_KEY: ${{ secrets.OCTOPERF_API_KEY }}
+          AZURE_CREDS: ${{ secrets.AZURE_CREDS }}
       - name: publish to Nexus
         run: .github/maven-central-deploy.sh
         env:

docs/guide/debugging/post-processor-debugging.md

@@ -11,6 +11,6 @@ DSL provides following methods to ease results and variables visualization and d
 :::
 
 ::: tip
-Remove such post processors when no longer needed (when debugging is finished). Leaving them would generate errors when loading generated JMX test plan or running the test plan in BlazeMeter or OctoPerf, in addition to unnecessary processing time and resource usage.  
+Remove such post processors when no longer needed (when debugging is finished). Leaving them would generate errors when loading generated JMX test plan or running the test plan in BlazeMeter, OctoPerf or Azure, in addition to unnecessary processing time and resource usage.  
 :::
 

docs/guide/jmx.md

@@ -36,7 +36,7 @@ If you use JSR223 Pre- or Post-processors with Java code (lambdas) instead of st
 
 ### Run JMX file
 
-jmeter-java-dsl also provides means to easily run a test plan from a JMX file either locally, in BlazeMeter (through [previously mentioned jmeter-java-dsl-blazemeter module](./scale/blazemeter#blazemeter)) or OctoPerf (through [jmeter-java-dsl-octoperf module](./scale/octoperf#octoperf)). Here is an example:
+jmeter-java-dsl also provides means to easily run a test plan from a JMX file either locally, in BlazeMeter (through [previously mentioned jmeter-java-dsl-blazemeter module](./scale/blazemeter#blazemeter)), OctoPerf (through [jmeter-java-dsl-octoperf module](./scale/octoperf#octoperf)), or Azure Load testing (through [jmeter-java-dsl-azure module](./scale/azure#azure-load-testing)). Here is an example:
 
 ```java
 import static org.assertj.core.api.Assertions.assertThat;

docs/guide/protocols/http/headers.md

@@ -31,5 +31,5 @@ testPlan(
 ```
 
 ::: tip
-You can also use lambda expressions for dynamically building HTTP Headers, but the same limitations apply as in other cases (running in BlazeMeter, OctoPerf, or using generated JMX file).
+You can also use lambda expressions for dynamically building HTTP Headers, but the same limitations apply as in other cases (running in BlazeMeter, OctoPerf, Azure, or using generated JMX file).
 :::

docs/guide/protocols/java.md

@@ -70,7 +70,7 @@ jsr223Sampler(v -> {
 ```
 
 ::: warning
-Using java code (lambdas) will only work with embedded JMeter engine (no support for saving to JMX and running it in JMeter GUI, or running it with BlazeMeter or OctoPerf). Use the first option to avoid such limitations.
+Using java code (lambdas) will only work with embedded JMeter engine (no support for saving to JMX and running it in JMeter GUI, or running it with BlazeMeter, OctoPerf or Azure). Use the first option to avoid such limitations.
 :::
 
 `jsr223Sampler` is very powerful, but also makes code and test plans harder to maintain (as with any custom code) compared to using JMeter built-in samplers. So, in general, prefer using JMeter-provided samplers if they are enough for the task at hand, and use `jsr223Sampler` sparingly.

docs/guide/request-generation/if-controller.md

@@ -43,7 +43,7 @@ ifController(s -> s.vars.get("ACCOUNT_ID") != null,
 ```
 
 ::: warning
-Using java code (lambdas) will only work with embedded JMeter engine (no support for saving to JMX and running it in JMeter GUI, or running it with BlazeMeter or OctoPerf). Use the first option to avoid such limitations.
+Using java code (lambdas) will only work with embedded JMeter engine (no support for saving to JMX and running it in JMeter GUI, or running it with BlazeMeter, OctoPerf or Azure). Use the first option to avoid such limitations.
 :::
 
 Check [DslIfController](/jmeter-java-dsl/src/main/java/us/abstracta/jmeter/javadsl/core/controllers/DslIfController.java) and [JMeter Component documentation](https://jmeter.apache.org/usermanual/component_reference.html#If_Controller) for more details.

docs/guide/request-generation/jsr223-pre-processor.md

@@ -56,7 +56,7 @@ post(s -> buildRequestBody(s.vars), Type.TEXT_PLAIN)
 ```
 
 ::: warning
-Using java code (lambdas) will only work with embedded JMeter engine (no support for saving to JMX and running it in JMeter GUI, or running it with BlazeMeter or OctoPerf). Use the first option to avoid such limitations.
+Using java code (lambdas) will only work with embedded JMeter engine (no support for saving to JMX and running it in JMeter GUI, or running it with BlazeMeter, OctoPerf or Azure). Use the first option to avoid such limitations.
 :::
 
 ::: tip

docs/guide/request-generation/loops/while-controller.md

@@ -46,7 +46,7 @@ whileController(s -> s.vars.get("ACCOUNT_ID") == null,
 ```
 
 ::: warning
-Using java code (lambdas) will only work with embedded JMeter engine (no support for saving to JMX and running it in JMeter GUI, or running it with BlazeMeter or OctoPerf). Use the first option to avoid such limitations.
+Using java code (lambdas) will only work with embedded JMeter engine (no support for saving to JMX and running it in JMeter GUI, or running it with BlazeMeter, OctoPerf or Azure). Use the first option to avoid such limitations.
 :::
 
 ::: warning

docs/guide/response-processing/jsr223-post-processor.md

@@ -41,7 +41,7 @@ jsr223PostProcessor(s -> {
 ```
 
 ::: warning
-Using this last approach is currently only supported when using an embedded JMeter engine (no support for saving to JMX and running it in JMeter GUI, or running it with BlazeMeter or OctoPerf).
+Using this last approach is currently only supported when using an embedded JMeter engine (no support for saving to JMX and running it in JMeter GUI, or running it with BlazeMeter, OctoPerf, Azure).
 :::
 
 Check [DslJsr223PostProcessor](/jmeter-java-dsl/src/main/java/us/abstracta/jmeter/javadsl/core/postprocessors/DslJsr223PostProcessor.java) for more details and additional options.