We have improved our authentication process and now offer a more secure way to log in with Two Factor Authentication (2FA). We also enhanced our Single Sign On (SSO) experience.
We’ve upgraded our engine images to support Taurus 1.13.7
In order to improve the product’s security, users with a “Tester” role won’t be able to modify the configuration of Private Locations.
We added the option to modify the columns size for the tests’ table in a project, so it is easier to look for tests with long data (name, description, locations, etc).
You asked for it, and now you can do it - we've added the ability to compare reports between different projects instead of limiting you to the specific project the report is located at.
We’ve made it easier to see where members in your account run their tests by adding the ability for account admins to see a graph representing the locations utilization spread between all the test runs in the account.
Any Ship that hasn’t been connected to BlazeMeter for over 3 months (e.g. server was offline, no network connection etc), will be marked as detached and unable to be used in the system for future test runs. If your Ship has been “detached” you will need to re-generate it or create a new ship.
Check out our sleek, new design in the top header for accessing your personal setting. Navigate from the top header to personal settings, to access the settings screen where you can change things such as your name and password.
You can now view all your account invites directly from the header. Just click on the envelope icon, and you’ll access the notifications. You can then choose to accept or decline.
We added extra filters to the admin view so you can now see results by workspace or by location.
We added a description column to the project page to make it easier to understand the tests created..The description is fetched from the test’s description which is added in the test creation page.
We’ve upgraded our engine images to support Taurus 1.13.6
We added two separate tabs for Functional and Performance Tests, so you can easily navigate between your functional and performance tests. When clicking on each tab retrospectively, the tests and reports are filtered, but the projects, workspaces, and all other account information can be accessed the same way.
You can now get a live view of the last 300 lines in you JMeter logs live for V4 tests. This can be found in the log tab, in application view of the tail, to allow for easier debugging.
For a BlazeMeter account admin, it’s important to have full visibility on the usage and resource utilization on the account level. The new admin view can be accessed from the top-right from any workspace dashboard, and allows account admins to see all tests that are currently running, including their details. Account admins can also choose to stop any tests directly in this new admin view. We are expanding this admin view to include more information such as location utilization.
Have access to tens of projects and you can’t find the one you are looking for? In order to help you navigate and find your projects, we’ve added a search capability in the projects page to easily find what you are looking for.
We modified the default location in the new created test to be US East (Virginia) in Google Cloud. You can then choose your desired location from the same list.
Need different engine sizes for different testing purposes? No problem! Account admins can now control the Engine size (CPU & RAM) and have different engine “types” from various locations. We will soon be adding the option so users with “tester” permission/role will not be able to access the Private Locations configuration.
New design and architecture for Remote Control update during test run allows you to update JMeter parameters for every scenario and location simultaneously. Furthermore, if a test has multiple scripts and locations, we will divide the RPS relatively between the scenarios and locations, according to the VUHs configured per location \ scenario
We’ve upgraded our engine images to support JMeter 5.1
Users now have full visibility & management on scheduled tests across each workspace they are part of.
For easier debugging and faster understanding of the issues in the test, we now upload JMeter log files periodically during the test
You’ve asked for it, and we’ve added support for both 1 sec and 1 min resolutions on the compare report.
We have now brought the scheduling capability to UI, allowing users to schedule their tests directly & simply from UI. If you need advanced configuration, you can set a cron syntax in under the advanced section.
The BlazeMeter Proxy Recorder now supports port 80 as well as random ports. iOS users can now use the Proxy Recorder for recordings by choosing the random port option.
Now, users will see a blue “Debug Run” stripe in the Original Test Configuration tab.
Now, the workspaces navigation dropdown supports inline search for workspaces. Instead of very long scrolling, users can now search to speed/simplify the effort.
The JMeter Properties section in the New Test Create will show users only the java versions that are relevant to their selected JMeter version.
The new environment page can be found in the account’s settings section, enabling users to configure a local plugins repository. At the moment, this page will be shown only for accounts with Private Locations and it includes the local JMeter repository configuration.
We’ve added the option to view your executive summary report directly from your report notification email.
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”.
File formats supported by the BlazeMeter JMX Converter:
Don’t miss these new features we have recently taken live:
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!
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.
We’ve upgraded our engine images to support:
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:
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:
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!
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.
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.
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:
Private Location status now shows who launched a test rather than who created it, so it’s easier to see who is using resources.
You can now choose which location you want to launch the Proxy Recorder from:
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:
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.
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.
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:
Now you can run tests on Azure (26 locations) from within the New Test Create (NTC) Beta.
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.
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 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.
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.
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.
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.
Our new API Functional Test feature continues to evolve at a fast pace. This sprint we’ve enhanced the new Import swagger file feature:
Look for “Import swagger file” in the (...) menu at the bottom of the Scenario list box:
Have a look at API Functional Test. Since our public release last sprint, we’ve been very busy:
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 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...
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:
Use our new intuitive UI to create API Functional Tests with or without writing code. Templates for authentication, variable extraction and dozens of other use cases make it fast and easy, whether writing your first test or your 100th.
Prefer to write code? Toggle between the UI and code editor with a click.
If you already have JMeter scripts or Taurus YAML scripts, just upload and run them to get detailed functional test results. Watch the animation below or read the help topic to learn more.
If you have an unlimited plan, you can now see how many parallel runs are operating across all workspaces in your account.
Hover over the green circled number showing tests running in your workspace to see the count of tests running in all workspaces.
In the report, we have converted the “Compare” and “Summary” buttons into icons, joining the Accessibility, Share, Refresh and Delete buttons which became icons a few releases back.
From today forward, you’ll see these icons and hover tooltips:
Now you can run JMeter 4, Java 9 and Taurus 1.10.5 on BlazeMeter.
We will deprecate JMeter versions <2.13 in April. When we do, we’ll execute these older scripts using the 2.13 engine. Now is a great time to check to see if your <2.13 scripts need edits to run on 2.13. JMeter is great at backward compatibility, but better safe than surprised :-)
We have updated our Sandbox location to be served from the following six IP addresses. If you have whitelisted our Sandbox location, you will want to update your whitelist to the following:
The Chrome recording extension has been upgraded:
CloudWatch now joins our other “inbound” APM integrations on the Timeline Report. Previously CloudWatch data appeared on a separate report tab. Enjoy the streamlined experience :-)
Ever wish you could overlay your own time-series data on the BlazeMeter Timeline Report? We’ll be releasing an API soon which lets you post JSON data to overlay on any test, even in real time. Watch for an update in the next release or drop a line to firstname.lastname@example.org if you want to get started right away.
The time-series resolution in the Summary report graphs now changes at the 5-minute mark:
Starting today, when you press the “Taurus” test create button, you’ll go to the New Test Create (NTC) screen being rolled out as part of our New Test Create Beta. For advanced users who have been running Taurus tests on BlazeMeter for some time, you’ll be interested to hear that the default execution framework is moving from “Taurus V1” to “Taurus V4” with this update.
We’ve been gradually rolling out a new test create workflow and underlying test execution architecture since earlier in the new year. Here’s a peek at what we’ve added in the most recent drop. If you have questions about the beta (including requests to join the beta and try it out so you can influence our final builds), please drop us a line at email@example.com.
The Debug Test button launches a quick run of your test at low scale to confirm that everything works from the cloud. Unlike the “sandbox test” feature in the previous version, with Debug Test, your settings (such as scale, location or duration) aren’t changed or reset in any way. We also write out a more detailed “trace.jtl” log for these runs to assist with troubleshooting.
When you upload a file in New Test Create, we validate the uploaded file, checking for:
The validation occurs automatically on file upload and you can re-validate on demand by clicking the “Revalidate” after making corrections/uploading new files.
This week we’ve added two new Google locations, Canada East (Montreal) and EU West (Netherlands). You can now choose from 56 cloud locations across Amazon, Azure and Google.
Sometimes it’s the little things that matter the most. This week we implemented two requests that were recently posted as feature requests on the Ideas Portal:
Long labels truncated? Just drag the column wider to see it all.
When you click on project name, it navigates you to the list of tests in your project.
Changes made to the selected KPIs on the Timeline Report are now “sticky” within the same report viewing session. For instance, if you switch from Timeline to Errors or Engine health and then back to Timeline, your KPI selections will remain as selected.
Now you can easily override or “offset” your local browser timezone setting for all time/date displays in the BlazeMeter UI. It’s also easy to toggle this feature on or off with a click.
Teams collaborating across times zones asked for this feature so they could discuss time stamps in reports without having to convert times in their heads. We are happy to provide it!
Navigate to: Settings > Personal > Personal Settings to set or toggle Time Zone Override:
Find a particular location faster, or filter the list to find locations with something in common by typing in the drop-down bar. Here we typed “lon” to quickly see which providers are supported in London:
We cleaned up the menu at top right of each report where you previously saw these six buttons:
The “Compare” and “Summary” buttons are still there, but we have converted “Accessibility,” “Share,” “Refresh” and “Delete” to icons:
Do you have many Workspaces? We’ve eliminated the need to download separate reports from each Workspace to track usage at the Workspace level. Look for the new “Workspace ID” column in the Account level Usage Report CSV. If you are have Owner, Admin or Billing role for your account, navigate to Settings > Account > Usage Report and click the Download CSV button:
Now you can view context-sensitive help, search our knowledge-base and more without ever leaving the app. Just click the green HELP CENTER tab on the right to get started:
We’d like to hear your voice! Want to suggest an idea for a new feature? Just click the Feature Request button in the new Help Center sidebar.
Everyone can submit ideas. Paid customers can also search, vote-up and subscribe to be notified of comments and status changes from within our new ideas portal. Learn more about the Ideas portal and your opportunity to impact our roadmap here.
Failure Criteria filtering is now available on both the Dashboard and individual Test History pages. The default view shows “All” and you can filter by “Passed”, “Failed” or “Not Set”:
We continue to expand our geographic diversity. Recently we doubled our Azure locations and this week we are adding Google’s Sao Paulo, Brazil location. You can always see the full list by viewing the locations drop-down in an test create/edit screen.
The Jenkins plugin for BlazeMeter is now workspace aware: select a workspace during job configuration to fetch tests specific to that workspace. We’ve also added average throughput and 90% response time to the metrics in the aggregate report.
Details and previous updates in the plugin changelog on github.
Now when you display the “Show all tests” or “Show all reports” lists, you can resize them to display long names without truncation. Just drag the border on the right:
The APM integration for CA APM is now bi-directional and uniquely smart. It's our first integration to import APM metrics without requiring you to specify the metrics ahead of time. CA APM identifies the systems impacted as your test runs and automatically imports the relevant metrics for you. There's no better way to keep up with an always changing environment. Just point to your CA APM instance, launch your test and we’ll take care of the rest.
Behind the scenes, BlazeMeter injects headers to your test traffic and CA APM determines which systems are impacted. CA APM then sends back the relevant metrics, which we make available in the Timeline Report. This new feature is layered on top of the existing outbound integration mode, where BlazeMeter test labels show up as Business Transactions in CA APM.
We have renamed the “Throughput RC” button to “Change RPS” to make it easier to find.
This button appears in tests where you have checked “Limit RPS” in the test configuration. It allows you to make mid-test changes to the RPS goal. See Limit RPS in the knowledge base for more detail.
We have re-designed the Stop Test dialog to make it more likely you will choose the “Graceful shutdown” option over the more destructive option, “Terminate servers”.
Workspace Alerts send alerts by email or Slack when test actions are taken and are triggered by size or duration thresholds. Now you can be notified of all test activity regardless of size or duration, by creating a Workspace Alert with duration set to "0" and concurrency set to "0".
To get alerts like this:
Create an alert (Settings > Workspace > Alerts) like this:
Tip: More detail on creating Slack Webhooks URLs for alerts has been added to our knowledge base.
We have renamed the “Multi Location” button to “Create CDN Test”:
This button appears in Test Configuration screens if your account plan includes this feature. Clicking it creates a 9-location multi-test designed to meet Content Delivery Network provider recommendations for an accurate test. Contact firstname.lastname@example.org if you have questions about this feature.
When viewing the test report, you can now easily filter the labels in the requests stats tab. Select the ‘settings’ icon found in the top right corner. In the pop up, under the select labels tab, select the desired labels you wish to see. Here’s a 25-second demo:
We have doubled the number of Azure locations, adding new locations in Korea, India, Australia, Canada, US and UK. Have a look at the locations drop-down to see them all.
We’ve added details about the test status, test name, script name, whether dedicated IPs are used and the status of each session - multi-location/multi-test. We’ve also enlarged the elapsed time indicator and moved links to learning resources to the bottom left.
Are you testing your system behind a firewall? You’ll be happy to hear that we’ve made the installation process of our on-prem testing much simpler.
We’ve updated the Usage Report both in the UI and the CSV document. Six columns have been added:
Note: You can enjoy the improved reporting abilities for data created as early as January 2017.
We’ve enabled adding OAuth tokens to your API tests.
We’ve added the ability to create tests for every operation in your API with the single click of button.
We’ve enabled executing API Quick Tests by using Private Locations behind a firewall.
We’ve added the ability to make changes to the API Key or Basic Auth for your API tests without having to regenerate all of your tests. Your authentication changes are automatically applied to your tests the next time you execute them.
New geo-locations available:
You can now run your BlazeMeter tests through Azure’s geo-locations.
Use the scripts from your shared folders while functional testing, to save time, reduce friction and improve your workflow
We would love to hear what you think.
Have you verified that your API isn't vulnerable to a SQL injection attack? The API Test Maker now lets you create SQL injection tests. Confirm that each endpoint in your API is safe.
You can still find all the good stuff in the Timeline Report:
Introducing Functional API Testing
1. Reuse your existing JMeter scripts and run them as Functional API tests, with the click of a button. Test single APIs or complete business scenarios and add them to your continuous testing process. You can also schedule tests to run periodically.
Functional API testing reports include: requests, responses, pass/fail indications based on assertions, and trends of multiple test executions. Read more here.
2. We’re also introducing the first version of the Functional API Test Maker for Automated Test Case Generation. Just upload your Swagger file and API testing scenarios will be auto-generated for you. Simply choose which of the scenarios to execute, at the click of a button or through your CI/CD process. You can also manually override or create tests.
Are your APIs complex? The Functional API Test Maker provides full test coverage.
New geo-locations available:
Do you need to update your company or personal details in your invoice? Now you can make the changes by yourself.
In the Billing section of your Account Settings we added a section for “Billing Details”.
You can add your Name, Email, Company Name, Phone, Address details and VAT Number.
As announced in our March 28 release, we will be deprecating existing API keys and moving to a new model that incorporates a key + secret and support for expiration dates to make them more secure. To make the upcoming deprecation process of the legacy API keys smoother, we added a new ability. Now, each user can disable their own API key.
Disabling Legacy API Keys can also be enforced by the account Admin. Just go to “General Settings” under the account settings.
We updated the Apache JMeter™ version choosing mechanism in BlazeMeter. From now on, the default version will be “Auto Detect”. This means BlazeMeter will automatically choose an Apache JMeter™ version according to your script. If you choose to, you can override that version by selecting a different version from the dropdown menu, just like before.
As part of our continuous effort to improve user experience, we updated the button you can use to invite users to collaborate. It now looks like this:
If you wish to upgrade your account, it is now easier than ever:
Check out our new API Keys on your personal settings tab in the settings section. As we’re going to deprecate the old API Keys on June 4th 2017, you'll need to generate new keys beforehand in order keep your API integrations working.
What’s new here:
Note that the API key secret is only available on key creation and we cannot restore it, so make sure you copy the secret and keep it safe!
Learn more about the new changes from these videos:
CA BlazeMeter added two new geo-locations:
In addition to many UI improvements, the following improvements and changes have been made:
In addition to many bug and performance fixes, the following improvements and changes have been introduced:
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