Changelog

Changelog

changelog

Don’t miss these new features we have recently taken live:

  • New Test Create (NTC) Multi-Test Is Here!
  • End User Experience Monitoring: multi-step scenarios
  • JMeter 5.0, Java 11 and Taurus 13.1 now supported
  • New setting in NTC: delay between requests
  • Usage Report CSV: “Test Ended” column added

 

New Test Create (NTC) Multi-Test Is Here!

 

The New Test Create (NTC) Multi-Test is here.  It’s never been easier to create multiple test collections that launch and report as a single test. Simply type a few characters to find the tests you want and add them.  Visualize the combined result, make local overrides and launch!

 

new test create, blazemeter

 

End User Experience Monitoring: multi-step scenarios

 

Need to monitor more than simple URLs - e.g. a page with login? Just upload one or more Selenium scripts recorded in Taurus YAML by the updated Chrome extension, enable End User Experience Monitoring and we’ll capture real-browser journeys throughout your load test.

 

end user experience, blazemeter

 

JMeter 5.0, Java 11 and Taurus 13.1 now supported

 

We’ve upgraded our engine images to support:

  • JMeter 5.0
  • Java 11
  • Taurus 13.1

 

New setting in NTC: delay between requests

 

When entering multiple URL/API requests in New Test Create (NTC), you can now add a delay between them by clicking on the “Scenario Definition” block:

 

New test create features, BlazeMeter

 

Usage Report CSV: “Test Ended” column added

 

usage report CSV

 

The Usage Report download CSV now includes a “Test Ended” column. Access the Usage Report in Settings > Account and Settings > Workspace (requires you to be an account admin or workspace manager, respectively).

Don’t miss these new features we have recently taken live:

 

  • Chrome Extension: Record JMeter and Selenium Simultaneously
  • Jenkins Plugin: Push Latest Test Files to BlazeMeter
  • Jenkins Plugin: Push Auto-Generated Test Data to BlazeMeter

 

Chrome Extension: Record JMeter and Selenium Simultaneously


BlazeMeter’s Chrome extension now allows you to record both JMeter and Selenium scripts in a single session. You can edit and debug Selenium scripts directly in the browser, run the recorded scripts on BlazeMeter or export scripts in JMeter (JMX) or Taurus YAML formats. It’s the perfect way to create End User Experience Monitoring journeys for real-browser performance during load tests. We have even more Chrome Extension features coming soon!

 

Jenkins Plugin: Push Latest Test Files to BlazeMeter

 

Use BlazeMeter’s Jenkins plugin to automatically update your test scripts before each run from your version control system (Git, GitHub, Bitbucket,...).

 

 

Jenkins Plugin: Push Auto-Generated Test Data to BlazeMeter


Also you can use the same setup (BlazeMeter’s Jenkins plugin and version control system) to dynamically push fresh test data to your BlazeMeter tests. Just generate the data, output it to your source control system or Jenkins workspace and let the updated BlazeMeter Jenkins Plugin push the updated data into your test configuration on each run.

From real-browser end user experience metrics to the latest features rolling into the “new test create” beta, there’s lots to see this week:

  • End User Experience Monitoring (Real Browser Metrics)
  • Report Actions Menu Moved, Tabs Restyled
  • Java Version Override, Sync Start and Transaction Details in New Test Create (beta)
  • Private Location Shows Who Launched Each Test
  • Proxy Recorder: Choose Where To Launch It From
  • API Functional Test Now Supports Custom JMeter Plugin Uploads

 

End User Experience Monitoring (Real Browser Metrics)

 

Now you can run real browsers during your performance tests to get End User Experience metrics. Watch the animation below or jump right to the Knowledge Base topic on End User Experience Monitoring.

 

blazemeter, end user experience

 

blazemeter updates

 

Report Actions Menu Moved, Tabs Restyled

 

To make way for exciting new reporting controls we will be adding soon, we have moved the actions menu and restyled the tabs in reports:

 

blazemeter reporting updates

 

Java Version Override, Sync Start and Transaction Details in New Test Create (beta)

 

  • Support for Java version override
  • Sync start (so all engines will start the test simultaneously)
  • Transaction components display: “Generate Parent Sample” will no longer be set to true by default, when uploading a JMeter script with a transaction controller.

 

Private Location Shows Who Launched Each Test

 

Private Location status now shows who launched a test rather than who created it, so it’s easier to see who is using resources.

 

Proxy Recorder: Choose Where To Launch It From

 

You can now choose which location you want to launch the Proxy Recorder from:

 

blazemeter proxy recorder updates

 

 

API Functional Test Now Supports Custom JMeter Plugin Uploads

 

Need a plugin to make your API Functional test happen? Now you can upload plugin JARs just as you’ve always been able to with performance tests. Here’s our shiny new Mainframe RTE Protocol plugin in an API Functional Test configuration:

 

blazemeter api functional testing

Here’s what’s new this week:

  • JMeter < 2.13 deprecated (Older tests now execute with 2.13)
  • Zoom synchronized across Timeline Report, Request Stats & Errors
  • Online Recorder whitelisting simplified: always uses port 8153
  • Azure available in New Test Create (NTC) Beta
  • BlazeMeter API V2 deprecated; “latest” now points to V4

 

JMeter < 2.13 deprecated (Older tests now execute with 2.13)

 

As of this release, we have deprecated JMeter engines with versions below 2.13. Any scripts that were created in earlier versions of JMeter will now be executed with 2.13.

 

Zoom synchronized across Timeline Report, Request Stats & Errors

 

Now when you zoom the Timeline Report graph, the sliders in Request Stats and Errors will follow the same selection. The reverse works as well: Moving the sliders will re-zoom the Timeline Report.

 

BlazeMeter updates, Zoom, timeline report

 

Online Recorder whitelisting simplified: always uses port 8153

 

The online Recorder now uses a static port number (8153), so there’s no need to whitelist a long range of ports in order to use it. We'll be changing it to port 80 soon to make it even easier. If you are new to the Recorder, have a look at BlazeMeter Proxy Recorder (Mobile and web) or just click the “Recorder” button on the Create Test screen to get started:

 

blazemeter, chrome recorder

 

Azure available in New Test Create (NTC) Beta

 

Now you can run tests on Azure (26 locations) from within the New Test Create (NTC) Beta.

 

run jmeter in blazemeter

 

BlazeMeter tests, azure

 

BlazeMeter API V2 deprecated; “latest” now points to V4

 

We have deprecated our V2 API and have pointed “latest” to our V4 API. This change was announced via email to all users of the V2 API in April.

 

Have a look at API Changes Effective June 10, 2018 if you need tips for migrating any remaining V2 or “latest” references in your code. Feel free to Contact Support if you have further questions.

Here’s what’s new this week:

  • Next Generation “URL/API Test” is Live!
  • New Relic Infrastructure Integration (RIP: Servers)

 

Next Generation “URL/API Test” is Live!

 

Do you love the ease and speed of our URL/API test feature, but wish for advanced features like assertions, variable extraction and file uploads in request bodies? Wait no longer! Most of the request editing features from our API Functional Testing UI have been added to the New Test Create (NTC) Beta. Watch the 30-second video below and read the docs for API Functional Testing to learn the finer points on variable re-use and such.

 

blazemeter updates, API functional testing

 

New Relic Infrastructure Integration (RIP: Servers)

 

New Relic may have shut-down the “Servers” feature in New Relic APM, but we’ve got you covered with our new integration to New Relic Infrastructure.  Overlay New Relic Infrastructure data on Timeline Reports for all test types to see what’s up on the back end. To get started, you’ll need a “Query key” set up in your New Relic Insights account.  Full details in our Knowledge Base.

 

new relic infrastructure integration blazemeter

Pages

DEVELOPER
X

Billing Information

Credit Card Information

Apply