Fork me on GitHub

News

Jagger 2.0 alpha release

29 November 2016

Jagger 2.0-m1 is the first point release of Jagger 2.0, our first major upgrade in three years. The main theme of this release is usability, which breaks down into the following areas:
- Simplified framework deployment using Docker containers
- Simplified programming model for load test development
- Better out-of-the-box Http protocol testing support
- Introduction of REST API for assessing test results

Framework deployment
From now on, deployment of the full Jagger framework in Docker containers will only take a few minutes. You will get all necessary infrastructure for test results storage, access, presentation, and sharing, including the Jagger Web UI and our new REST API service - JaaS (Jagger as a Service), which will provide the REST API for test result access and report generation

Load test development
We have prepared a new test project template. Now you can develope your tests in pure Java. The description of the full load test for some API endpoint will take only six lines of code. Template will work with Docker containers out of the box; no additional configuration is required. You can start your first performance test with just three commands

Http protocol support
We put extra effort into simplifying the http load test implementation. Our http library, based on the Spring http client, will help you to manage input test data, provide communication with SUT, and verify responses

Try our new version at http://griddynamics.github.io/jagger/doc/index.html

Known issues in alpha release:
- Docker containers with MySQL take a long time to initialize during the first launch. At the moment, there is a one-minute delay after starting applications before they work with MySQL
- When WebUI is launched with an empty test results database it will through ?no session information found? exception. Just run the load test to populate DB with the test results and update WebUi in your browser
- It is not possible to download pdf report via Swagger UI of the JaaS REST API due to the Swagger issue. However, you can download reports in your browser

Jagger Release 1.2.6

8 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 tests 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

For all teams, who are using Jagger, we are recommending to switch to 1.2.6 version, before migration to Jagger 2.0

Announcement of the new Jagger 2.0 alpha release, will come soon together with the updated documentation

Continuous performance testing

13 April 2015

Why Continuous Performance Testing (CPT)
- We want to catch performance issues earlier
- We want to catch performance issues faster
- We want to see trend of our results

What we mean when speaking about CPT
- Performance tests are executed regularly in CI environment (with every code update or periodically)
- Results of performance tests, including resource utilization, are automatically evaluated
- Results are compared to some limits. When results are out of limits, alerting is enabled
- There is central storage for results. Both aggregated data and detailed results are stored for analysis
- It is possible to compare results from different sessions

Learn more about our vision of CPT and how jagger can help you to setup this process

Get acquainted with Jagger

27 February 2015

Easy, step by step guide how to get acquainted with Jagger features:
- Generate load
- Create PDF report
- Monitor system and JVM metrics
- Store results
- Review and share results
- Setup acceptance criteria for results
- Run continuous performance testing

See details on Documentation page

Jagger framework for user scenarios testing

13 October 2014

Testing of web services looks like a simple task. Single request - single response. Every instrument for load testing can do it.

Much more complicated is to run user scenario test - sequence of particular user actions on some web site. And today we are proud to say that Jagger is able to provide such tests. Thanks to Jagger flexibility, when you can customize every component of the framework, and after introduction of Listener and Services, that provides simple interface for customization, it is possible to use framework for acceptance testing of full eCommerce site.

With implementation of two custom components: invoker and invocation listener, we were able to run following user scenarios during performance testing:
- Registration of new user and login
- eCommerce site browsing and search
- Checkout with updating contents of the cart

Our test included:
- Managing user sessions with cookies
- Provide asynchronous calls to services
- Manage SSL connections to self-signed certificates on test environments
- Measuring, storing, evaluating response time percentiles of every step in scenarios
- Providing functional testing of every response in scenarios
- Measuring application specific trends. As example - checkout scenario with different number of products in the cart

Jagger Release 1.2.5

8 July 2014

Main goals for release 1.2.5:

- Jagger performance testing framework from the very beginning was designed to meet requirements of Continuous Performance Testing.
Efficient data storage and representation, integration with Jenkins, automatic decision making allows to use Jagger in Continuous Integration
environment from the box. In this release we introduce new enhanced functionality to make decisions. With simple setup it is now possible
to make decision about test execution status based on latency and throughput metrics, system resources utilization, custom metrics, results of functional tests.
To learn more, please refer to documentation page Making decision based on limits for measured parameters

- We are continuing to implement approach with Listener and Services.
In this release we are introducing new service - DataService. It provides access to measurement results from custom code. One can get full information about test sessions, executed tests and all measured metrics via simple API

- Another topic for this release - improvement of measured data representation in Jagger Web client. Take a look on new plots representation with ability
to download pictures and plot data as CSV, change layout of plots and amount of displayed information

Release Notes: Release notes
Presentation: Release presentation

Jagger Release 1.2.4

7 April 2014

Main goals for release 1.2.4:

- Mission of Jagger performance testing framework is to help our users to develop efficient, reliable, high-performance applications
Spending large effort to follow our mission, implementing new features, we sometimes forget about performance of our own application
So this release we dedicated to improvement of Jagger efficiency. First task was to speed up data fetching for our Web client. Second - to
aggregate and save test data faster. Both tasks are finished and we are inviting your to verify results of our work.

- In this release we also introduce InvocationListener. With this step we are developing our idea to make Jagger more flexible, but keep it simple
What is behind this idea? With introduction of Listeners we gave simple mechanism to trigger user actions during workload execution.
We have implemented listeners for test suite, for test groups, for tests and single invocations. All interfaces are following same stile and conventions.
Thus you need to learn once how to create listener and later use this knowledge for all interfaces.
Inside listeners you can use Jagger services. They provide easy way to create and save test metrics, save comments or mark session with tags. How services and listeners are working together you can see in examples from our archetypes

- Starting from now it is possible to provide user comments to you test results directly from Web client
Also there is possibility to mark sessions with user defined Tags and later filter sessions in Web client by these Tags
More detailed information about mentioned features you can find in docu

Release Notes: Release notes
Presentation: Release presentation

What is Jagger ...

22 January 2014

Want to understand what is Jagger, get fast overview of the tool, learn about main features?
Watch new infographics

Jagger Release 1.2.3

22 January 2014

Main goals for release 1.2.3:

- We want to make our instrument more flexible, but keep it simple. To meet this requirement we are introducing Listeners and Services
Listeners allow to provide user actions triggered by test events such as test start/stop, test group start/stop, etc
Services, available in Listeners, give simple access to internal components of Jagger, f.e. to store internal metrics from System Under test, make additional Session comments
Approach for implementation of Listeners and Services is very simple and requires small amount of custom code
In future releases we will expand list of available services to give our customers new functionality
- We have introduced new tree view control element to Jagger WebUi. Control of all tabs is now much simplier and handy

Release Notes: Release notes
Presentation: Release presentation

Jagger Release 1.2.2

5 November 2013

Main goals for release 1.2.2:
- Further improvement of custom metrics collecting, validation and reporting
- Enhancement of summary data representation in webUI

Release Notes: Release notes
Presentation: Release presentation

Jagger on SQA-Days

2 April 2013

Jagger is going to be presented on SQA-Days'13 on 26th of April 2013. SQA-Days (Software Quality Assurance Days) is largest conference in the CIS and Eastern Europe on software quality assurance.

Jagger Release 1.1.3

19 March 2013

Finally we have released version 1.1.3 which contains:

  • Conceptial change in configuration, it became more friendly and less complex.
  • Jenkins plug-in to deploy and run Jagger.
  • Samples distributed as maven archetype.
Full Release Notes can be found here. From the other hand Jagger documentation was updated and reworked. Next release is going to be in production in the first week of May 2013. We plan to improve webUI and add more Samples.

Jagger future plans

05 November 2012

Jagger team recieved a lot of comments and feedback on product from different project. We take time to aggregade and define goals for next release. For now we can say that we will work on usability/configuration improvement and continue to collect your feedback.

GridDynamics releases Jagger to public

16 November 2011

GridDynamics, a leader in scalability engineering, makes its performance testing suite free for everyone. Jagger was developed internally by GridDynamics to control quality of mission-critical services that GridDynamics delivers to its clients. This suite reflects years of hands-on experience in consulting, development, and production support of high-performance applications and realizes best practices of continuous delivery and quality assurance.

Jagger presented on additional session of HighLoad

5 October 2011

Jagger was presented on additional session of HighLoad++ conference.