Here is what’s new with the November 18th release:
- Add a test to a Multi-Test (NTC) that’s already running
- Improved JMX Converter at converter.blazemeter.com
- Enhanced TeamCity plugin (version 2.3)
Add a test to a Multi-Test (NTC) that’s already running
One of the features long-time BlazeMeter power users love is the ability to add additional load or entirely new test logic to a large test that’s already running. No need to stop, reconfigure and re-launch: Just launch an additional test and join it to the Multi-Test in progress. This feature is now live in New Test Create (NTC), also known as BlazeMeter “V4”.
Improved JMX Converter at converter.blazemeter.com
- Massive performance improvement - a 30MB file is converted in about 15 seconds!
- Improved support for PCAP files
- Improved file type detection
- New UI with a fresh & clean look:
File formats supported by the BlazeMeter JMX Converter:
- HAR JSON - from Mozilla Firefox traffic
- XML from Internet Explorer
- Selenium Builder input
- PCAP input
- JSON from the BlazeMeter Chrome Extension, HAR and Selenium Builder
Enhanced TeamCity plugin (version 2.3)
- You'll find a separate BlazeMeter tab in build results that contains a summary of the build and link to the BlazeMeter report
- Workspace selection added to build configuration
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!
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.
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:
Usage Report CSV: “Test Ended” column added
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
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.
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:
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:
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:
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.
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:
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.
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.