What's New in JMeter 3.3?
What's New in JMeter 3.3?
Learn about the features and changes you can expect when updating to the new version of the Apache JMeter performance measuring tool, version 3.3.
Join the DZone community and get the full member experience.Join For Free
xMatters delivers integration-driven collaboration that relays data between systems, while engaging the right people to proactively resolve issues. Read the Monitoring in a Connected Enterprise whitepaper and learn about 3 tools for resolving incidents quickly.
JMeter 3.3 was released by the Apache JMeter™ team at the end of September. This upgrade is part of JMeter's progress and quality improvement to remain a modern and updated load testing tool. This release follows quite a few releases in the past year: JMeter 3.0 was released a year ago, in September 2016. It was upgraded to version 3.1 in November 2016 and to JMeter 3.2 in May 2017. Read this blog post to learn everything you need to know about JMeter's new version.
The implementation menu box was removed because JMeter supports only one HTTP Client implementation, making the UX cleaner.
Now you can see the results of the function JMeter generates, in addition to the function. This can help you understand how JMeter generates function results for you, and improve your knowledge of how tests are run.
Here's how it works:
- Options-> Function Helper Dialog
- Choose a function.
- Configure the function values.
- Click "Generate".
- You will see the function to be used in JMeter, like before, and also a preview of the results.
By clicking "Generate" again you will see more results.
You can now load test the Brotli Compression by adding the "br" encoding value to the HTTP Header Manager.
In the past, Vary header responses weren't cached at all. Now they are. Good news for users who use advanced HTTP caching features.
In the past, some threads that were interrupted in the middle of a transaction weren't reported anywhere. Now, this has been fixed. Interrupted transactions are reported in success and failure reports, for a more accurate load test analysis. This fix was contributed by BlazeMeter.
In the past, if you ran a test that had threads that were sleeping on timers, and you stopped the test or it was interrupted, all of the sleeping threads would be released at once. This created a huge spike that could crash your target environment. Now, this bug is fixed, and if you stop a test, sleeping threads stay connected to their timers.
Read about all the fixes in this version, here.
Get free JMeter training from our JMeter academy. Whether you're a beginner or an advanced user, master your open source load testing.
Published at DZone with permission of Noga Cohen , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.