2.2

This release adds support for the WebSocket protocol, allowing you to connect and send/receive text messages.

It also fixes an issue affecting the OctoPerf integration.

2.1

This release upgrades the Parallel Controller to version 0.12 due to an issue with JMeter 5.6.3 in the previous version.

2.0

This release upgrades the underlying JMeter version to 5.6.3.

We've incremented the major version to 2.0 due to a breaking change introduced in JMeter 5.6.1, where the default character encoding behavior was modified. This change could impact applications that depend on specific encoding configurations, making it potentially non-backward compatible.

1.30

This new release allows you to disable keep-alive in HTTP requests, and now you can use the Weighted Switch controller with the random option.

Thanks for your contribution @rsiatka and @KopysovDB

1.29.1

This release just avoids the warning about deprecated Nashorn JavaScript engine when running JMeter tests

1.29

You can now add custom labels to variables setting to ease identification of multiple variables setting elements thanks to @andy-tarr.

Additionally, this release updates urls generated by OctoPerfEngine to point to the latest OctoPerf UI.

1.28.1

rpsThreadGroup now does not make samplers or other parts of testplan fail when the test plan is ending.

Thanks to @simonNeir to raise this issue.

1.28

You can now publish Prometheus metrics with prometheusListener! Check the new user guide section.

Additionally, you can use showTimeline at test plan level to review, while designing a test plan, the thread groups planned load in a time line graph. This is more convenient than using existing showTimeline in each thread group.

Thanks to @rahul84gupta and the rest of people requesting the Prometheus listener.

1.27

In scenarios where you need more control over responseFileSaver generated file names, you can now use autoNumber and autoFileExtension methods to disable the default behavior.

Thanks to @Pyrobow for this contribution!

1.26

Updated selenium driver, used in jmdsl recorder, which was no longer working with latest versions of Chrome.

To use the recorder and jmx2dsl you now need to use JVM 11+.

For the rest of the cases, which are the most cases as like just using jmeter DSL without recorder or jmx2dsl, you can still use JVM 8.

We have additionally included some user guide fixes and clarifications, and added support for deserializing ContentType class to be able to support methods using it from other languages (mainly JMeter .Net DSL).