Skip to content

Release 1.2.6

Dmitry Latnikov edited this page Dec 2, 2016 · 1 revision

Jagger 1.2.6 Release Notes

8th November 2016

We are happy to announce coming Jagger 2.0 - scalable service for continuous performance testing. Keeping existing key feature like: rich monitoring capabilities, automated decision making, functional verification during performance tests, customization options, data representation and reporting, we are introducing new Jagger service for real time orchestration of the performance test and test data management

In Jagger 2.0 all components, available as docker images, will simplify performance infrastructure deployment. New pure java test configuration, based on the rich library of the build-in components, will allow fast creation of the new test suits. New Jagger service with REST API will help our customers to build efficient continuous performance test pipelines

Before major release, we finalize our work on the previous version and today we are releasing 1.2.6. While there are no large features introduced in this release, we are bringing multiple enhancements:

  • Performance of the test results aggregation, write and read access is significantly improved
  • New algorithm with active feedback for Requests per Second (RPS) load strategy fast and accurately adjusts load for the system with variable response times
  • Jagger WebUI test results representation is improved
  • Defects are fixed

What's new:

* [JFG-833] - New improved algorithm with feedback for Requests per Second load strategy

Improvements:

* [JFG-425] - Expand docu for Configuration xml schema
* [JFG-596] - Improve standard metrics aggregation / read from DB performance
* [JFG-914] - Change plot Y scale when lines are removed/added
* [JFG-915] - New standard metrics: Success rate, Number of fails, Number of virtual users

Bug fixes:

* [JFG-808] - UI problem with link wile selecting metrics for summary table
* [JFG-817] - Test listeners are not inherited from parent elements in XML scheme
* [JFG-895] - Jagger uses one-by-one load balancer instead of round robin.
* [JFG-896] - Jagger sometimes uses single color to display different metrics on a graph