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.

 

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.

 

 

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.

 

Here’s what’s new this week:

 

1. Add a Description To Your Tests
2. Single Sign-On/SAML Enhancements
3. Dynatrace APM Now Bi-Directional (Populate Timeline Graphs)
4. API Functional Test - Swagger Import Improvements

 

Add a Description To Your Tests

 

By popular demand, test configurations now have a “description” field, where you can document the scope or purpose of your test. No more “LongTestNameTryingToTellTheWholeStory” required!

 

 

This feature is available in JMeter Test (new), Taurus and API Functional Test flows.

 

Single Sign-On/SAML Enhancements

 

We’ve listened to feedback from our single sign-on (SSO) customers who wanted greater control over new user accounts and no more “pile up” of new users in the default workspace.

 

1. Now you can turn off the “default” workspace, so users can only use BlazeMeter if they have been added to one or more workspaces by an admin. With this option, users who have not been assigned a workspace will get a splash screen asking them to contact the admin for access, instead of landing in a default workspace with full entitlements.
2. Want to add user accounts without depending on email invitations for users to read and respond to?  Check! Now you can create and activate accounts entirely from the admin side.

 

Dynatrace APM Now Bi-Directional (Populate Timeline Graphs)

 

Our integration with Dynatrace is now bi-directional!  You’ve always been able to send “red dye” (decorated headers) outbound to make test traffic easy to see in Dynatrace and now you can pull Dynatrace metrics inbound to visualize in Timeline Graphs. This is also the debut of Dynatrace support in our new test create (NTC) screens. We’ve made this new functionality available in both our legacy and new test create (NTC) screens.

 

 

API Functional Test - Swagger Import Improvements

 

Our new API Functional Test feature continues to evolve at a fast pace. This sprint we’ve enhanced the new Import swagger file feature:

 

1. Parameters are now converted to variables, so you can easily populate them with test data from a CSV file.
2. Base URL (default address) and base path (default path) are saved in global variables.
3. Now you can cancel import of swagger file mid-import if needed.

 

Look for “Import swagger file” in the (...) menu at the bottom of the Scenario list box:

 

 

Here’s what’s new this week:

1. API Functional Test: we’ve been busy :-)
2. Reminder: JMeter <2.13 will be deprecated April 29th
3. Usage Report now shows if run from UI, API, Jenkins, etc...
4. Bamboo plugin updated: New “BlazeMeter Test Report” tab

 

API Functional Test: we’ve been busy :-)

 

Have a look at API Functional Test.  Since our public release last sprint, we’ve been very busy:

• Import Swagger (Open API) files to create scenarios: import all verb + endpoint combinations or only selected ones
• Use test data from CSV files
• Dynamically pull file content into request body
• Add file attachments (binary files) to requests
• New request methods (PATCH, OPTIONS, HEAD, CONNECT)
• Text type assertions - define assertions without the need to know regular expression syntax
• JSONPath value assertions - assert the value found at the defined JSONPath
• Response time assertions for individual requests
• Common functions - generating random numbers or random strings for parameters in your test or base64 or URL encoding strings
• All private locations are available from the UI for API Functional Test
• Download test script from the UI (Taurus YAML)

 

Reminder: JMeter <2.13 will be deprecated April 29th

 

We will deprecate JMeter versions <2.13 on April 29th.  When we do, we’ll switch to executing these older scripts with the 2.13 engine.

 

Usage Report now shows if run from UI, API, Jenkins, etc...

 

Usage reports now include an “Execution Client Id” column so you can see at a glance whether test was run from UI, API, Taurus, Jenkins, etc...

 

Bamboo plugin updated: New “BlazeMeter Test Report” tab:

 

Jump to detailed BlazeMeter reports right from your Bamboo build dashboard with the new BlazeMeter Test Report tab.

 

 

Learn more about the Bamboo plugin for BlazeMeter:

• BlazeMeter Plugin to Bamboo
• BlazeMeter Bamboo Plugin on GitHub