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 email@example.com 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 firstname.lastname@example.org.
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: