What’s New in Open Source Taurus 1.13?
Taurus version 1.13 was released on September the 4th. This new version has many major and impactful changes in it: we have added more testing abilities, improved our internal performance, and made installation and usage more aligned with the open source tools we support. Many of these additions and fixes came from users’ requests on support forums, which is part of our commitment as an open source tool, to the community. You can participate in our support forums here.
Here are the top 4 changes in Taurus 1.13. Read the full changelog here.
Top 4 Taurus 1.13 Upgrades
1. Windows Installer is Now Self-containing
You can now install Taurus on Windows without needing an internet connection. In the past, Windows users needed a network connection to install Taurus with the Windows Installer, so they struggled if they had corporate proxy requirements or no network connection at all. Not any more: users just need to download the installer in advance, and they can run it without the network connection. More details here.
Please note! Users can't just seamlessly use the new installer to upgrade the older Taurus installation, because we have changed the installer technology. Please uninstall the old version first, and only then install the new one. Uninstalling is only required for this upgrade, subsequent Taurus upgrades should work fine.
2. Added Support for JUnit 5 and Concurrency Abilities for the JUnit Executor
There have been several requests on support forums and from customers to support JUnit 5, the next-gen of JUnit. Now we do! To switch to JUnit 5 from the default JUnit 4, use the special flag in the config.
Another JUnit improvement we added compares Taurus abilities to HPE’s Performance Center: you can now run JUnit tests in Taurus concurrently. Just add `concurrency`, `ramp-up`, etc., and you will get as many JUnit's running in parallel as you want. But beware, JUnit is not as modest and moderate as JMeter in terms of RAM and CPU it spends per VU. Achieving higher concurrency might require BlazeMeter cloud scaling.
3. JMX Modified to Match JMeter
When developing Taurus we thought we should improve some of JMeter’s shortcomings. However, time has shown that users don't accept these corrections as natural. We originally thought that forcing a parent flag on the Transaction Controller would help avoid misleading results due to the double count of the same request. We also thought that historical inclusion of of Apache JMeter™ connect time to latency needs "fixing" on Taurus’s side, by subtracting the connect time from latency.
We hear our users and customers, so we are turning these "fixes" off. Now, the behavior of JMX files execution is now more like it is in bare JMeter.
4. Taurus Performance Boosted
Due to heavier and heavier Taurus usage in the BlazeMeter cloud, thanks to widespread BlazeMeter V4 adoption, we have faced performance issues inside Taurus’s aggregator subsystem.
In the past release we made some optimizations, but they were not enough. We have also occasionally dropped the `stdev` KPI from the aggregate XML dump. (This can happen for any software project!). So in this release, we’ve restored `stdev` and performed double the optimization in the aggregator subsystem.
Now Taurus performs the heaviest part of its calculations only once the corresponding KPI is queried. This brought a significant boost for tests with lots of sample labels.
Additional fixes and additions to this Taurus version include:
- Bumping up the default ChromeDriver version to 2.40
- Using Google Iowa as the default Cloud location, instead of Sandbox
- Fixing Swagger2YAML converter crashes
- Fixing the handling of the body string in the Gatling script generator
- Bumping up the Plugins Manager version to 1.3
Read the full list here.
Start testing with Taurus now and easily create, run and analyze tests from 20+ open source testing tools for free.