Blazemeter Logo


Release Date: Monday, August 22
  • BlazeMeter Added Two New Geo-Locations
    • AWS India (Mumbai)
    • GCE US West (Oregon)
  • Major performance improvements in viewing test results
  • Multiple bug fixes in the following sections:
    • Executive Summary
    • Statistics Calculations
    • Aggregate Report
    • Error Report
    • Taurus Tests
  • The Personal Settings Dialog got a facelift
Release Date: Wednesday, July 13
  • BlazeMeter web application is now WCAG 2.0 compatible.
  • Testers can increase the number of concurrent users in running large scale tests.
  • Zooming-in on a specific timeframe in the aggregate report shows calculated percentiles.
Release Date: Tuesday, June 28
  • BlazeMeter adds support for JMeter 3.0!

  • Usage report available: Now you can clearly view your test run history on a graph and export it in CSV format for further analysis

  • Updated usability on the multi-test configuration page. Now you can:

    • Easily view how many scenarios will run, their duration, geo-locations and names

    • Easily view each scenario’s name, type, geo-location, number of virtual users and duration

      JMeter load testing scenario



Released in 2016, prior to initiation of Changelog with Tuesday, June 28 Release
  • Ability to pause ramp up, and later resume ramping users while test is running.

BlazeMeter load testign


  • Added packet-loss ratio to network emulation controls, to better support mobile application testing:


Mobile app testing



  • Added ability to select a specific time span for the aggregate and error reports. Drag sliders to focus on a key period or eliminate ramp-up/ramp-down periods.



JMeter - Aggregate reports


  •  Added scenario and location filters to timeline report to provide finer granularity of data on multi-test and multi-geo tests.


Load Testing KPIs



  • New Relic data now appears directly on the Timeline Report to support visual correlation with test data.  This eliminates the need to switch tabs to see New Relic data during tests.
  • Added ability to create Taurus tests from the Web UI:



JMeter Performance Test



Taurus test automation


  • Added new geo-locations:
    • All MS Azure locations (initially as beta)
    • AWS: South Korea, Germany
  • New locations drop-down list (shows which location has dedicated IP addresses available)


Load testing locations


  • Multi-tests can now be duplicated in a single operation.
  • Complete refactor of 'original test configuration' tab in the report screen, based on user feedback.
  • New view for billing-info page



JMeter load test


  • For clients who have chosen server-hour billing, the usage report now shows consumed and remaining server-hours instead of test credits consumed. 


  • Enhanced Organization Support
    • Organization usage report - now organization administrators can view the subscription usage of the entire organization.
    • Added support for user to manage multiple organizations.
    • Tests can now be moved between organizations.
    • Consistent organization context switching: switching organizations now updates all drop-down menus, lists and selectors to reflect the chosen organization.
    • Added 'start collaborate' button in app top header to introduce users to Organizations capability and make creating organizations easy:


Load Testing


load test collaboration


  • Adding support for Gravatar (displays your avatar image from if login email registered in a account)
  • Separation of workspace settings and user settings.
    • Workspace settings are on a dedicated "Settings" tab alongside Dashboard and Project tabs:

Performance test report



  • User settings are now an overlay dialog, launched from by choosing "My Settings" in the top-right navigation menu:

Performance Testing



  • New drop-down list in top header for 'recent projects' – chose a project or select "Show all projects" to display a full-page list.
  • Many screens now have unique and descriptive '<title>' to ease navigation via browser history.
  • Java 8 - which supports SSL TLS 1.2 (This is new standard for web servers. Many tests previously failed due to the lack of SSL TLS 1.2).