1.24

You can now set the percentiles you want to send in influxDbListener thanks to the contribution of @ndanilin.

Included some refactors contributed by @Kabilesh020799.

And added the possibility to set a maximum time for execution in thread groups when iterations are set thanks to the request of @Melanie-RK.

1.23.3

This release fixes backend listener jar resolution, and in particular elastic search listener showInGui method.

Thanks to discord user onebyy for reporting this bug.

1.23.2

This release fixes a bug that causes httpHeaders not to work properly when in multiple levels of a test plan that contains a jsr223Sampler. Here is the reported issue.

Thanks to @FakeLogin for pointing to this bug!

1.23.1

This includes a small fix in EmbeddedJmeterEngine to avoid JMeterUtils warning when running a test plan

1.23

Now jmx2dsl support converting test plans with JDBC samplers using a JMeter expression (eg: ${QUERY}) as query.

Thanks to @geoe6 for requesting this.

1.22

You can now set maximumValue, increment and perThread settings in counters.

Thanks to @rsiatka for requesting this.

1.21

You can now use simpleController to apply timers, listeners, assertions, configs, pre- and post-processors to parts of a test plan!

Check the updated user guide section for more details.

Thanks to @ben-norton-anaplan for the contribution and @FakeLogin @andy-tarr for helping with design decisions.

Additionally, bridge service now supports deserializing properties which require multiple invocation of property methods (like rampUp in threadGroup).

1.20

Now is possible to properly parse enums properties sent to bridge service. This is necessary to add support for regex extractor features in .Net DSL.

1.19

You can now automatically stop test plan execution when collected metrics condition is met!

Check the new user guide.

Thanks to @mikeliucc, @kirillyu and Woweyn and Ivan Smolin from Discord asking for this feature support.

Additionally:

• AzureEngine now automatically uploads JMeter DSL artifacts to Azure Load Testing test when needed.
• Fix jsr223Sampler naming.

1.18

AzureEngine now automatically uploads csvDataSet and httpSampler files to Azure Load Testing!

Additionally you can now:

• Set name of test run
• Configure monitored resources (application components)
• Specify to split CSVs between engines.

You can check the updated Azure user guide section.

Thanks to @mikeliucc for requesting these features.

Finally, AzureLoadTesting updates of test plan has been fixed due to previously incorrect test plan validation check logic, and some minor fixes have been included in user guide & exception thrown by thread groups when using iterations after ramping threads.

Thanks to @mikeliucc and @pjcalvo for pointing for the potential improvements.