Blazemeter Logo


What's New for October 2021?

[Mock Services] Regular Expressions with XPath and JSONPath 

Transactions now support a new in-house format of XPath and JSONPath matchers. You can use Regular Expressions together with XPath and JSONPath. See the documentation for more info. 

[Mock Services] Number of Hits in Mock Services List

The number of requests that hit a Mock Service during its lifetime is now displayed in the Mock Services list. This helps to quickly identify which Mock Service is in active use and utilized.

[Mock Services] Inline Editing of Transactions in Mock Service

The Mock Service details window now lets you edit transaction definitions directly from the Transaction shuttle control. It is no longer necessary to switch back and forth between Mock Services and Asset Catalog screens when you need to edit transactions for your running Mock Service. For more info, see the documentation.

Inline Editing of Transactions in Mock Services

What's New for August 2021?

[General] Crane Logs 

Private Location Manager: The Agent Log
To investigate agent failure, view the logs and debug issues in real time, you can now enable the agent log for your existing private locations. For newly created private locations, the agent log is ON by default. You can also download the agent log file for the last two weeks. For more information, see the documentation.


[GUI Functional] New browser added - Microsoft Edge 

In addition to Chrome and Firefox we’ve added Microsoft Edge. This is Chromium based Edge, which runs in Linux OS. Now you can run your GUI Functional tests in Microsoft Edge browser, which is already available on Public Locations.

For Private Locations, just select Microsoft Edge at Functionalities tab of Private location configuration. If you have auto update disabled for your Location, you will need to install the image manually.

New Browser Added - Microsoft Edge


[Mock Services] Export All Transactions in a Service to JSON


You can now export all Transactions that are under a specific service to a JSON file. You can also import all the Transactions that are in the Exported JSON file.

To learn more, see the documentation.



[API Monitoring] [API Testing & Monitoring] API Monitoring Test Results API Enhanced to include Subtests Details

In BlazeMeter API Monitoring tests, Subtest steps can run other BlazeMeter API Monitoring tests as part of a test run. This is useful for reusing tests that perform common functionality like generating a new access token, setup/teardown or creating suites or groups of tests.

The Test Results API has been enhanced to also list the total number of Subtests, the number of Subtests passed and failed and details of each Subtest step including the name, result, Test Ids and start and end times.

 API Monitoring Test Results API Enhanced to include Subtests Details

What's New for July 2021?

[Performance/Taurus] Automation Enhancement: Fail tests against the Baseline when running from Taurus

One of the most useful things about having a baseline to compare with, and fail the test in comparison to it (baseline-based failure criteria), is to have more accurate failures when automating your tests. 

If you are automating your BlazeMeter tests via Taurus (running on the Cloud), now you can define baseline-based failure criteria in the YAML and have your test fail automatically in BlazeMeter. 

Check out BlazeMeter documentation to learn more about this feature. 

Automation Enhancement 


[Mock Services] Helper Wizards for Request Matching and Dynamic Response Creation

The help wizards for XPath and JSON Path help you generate XPaths and JSON Paths for request matchers in a transaction so you don't have to enter the path manually. Just specify what type of value to match in tree-based selection fields and the path is generated for you.

The help wizard for responses helps you create dynamic values (Magic Strings) in the response content. The information is pulled from the request and rendered on the response so you don't have to worry about entering the syntax manually. 

Check out the docs to learn more.


[Mock Services] Cloning Transactions


You can now clone Transactions that are under a specific service to a new service. You can also find and replace a specific text in Transactions while cloning. Moreover, you can create a Mock Service that contains all the transactions that have been cloned.

Check out the docs to learn more. 


[Mock Services] OpenShift Support for BlazeMeter Agent for Kubernetes

Mock Services now support the OpenShift Container Platform web console. You can create a new project, create a role for an agent and deploy the agent using OpenShift. You can then deploy Mock Services to your Private location as usual.

Check out the docs to learn more.


[Mock Services] Rename or Delete a Service

If you are a workspace manager or an administrator, you can now rename and delete services. See the docs for more info.


[Mock Services] Dependency on SV Bridge Component Removed for BlazeVSE

We removed the dependency on SV Bridge component for BlazeVSE. You don't need to enable SV Bridge anymore unless you want to use that bridge to connect to enterprise SV. More info here.

What’s new for June 2021?

[GUI Functional testing/Taurus] Added ability to pass browser options via YAML file

During GUI Functional testing, you may need to configure your browser for specific cases, like emulating mobile devices in the browser, or emulating web cameras and many more. This can be achieved by passing appropriate browser options/arguments, or even experimental options. The Taurus YAML file syntax now allows you to pass such options to the browser:

[GUI Functional testing] New browser versions now available 

We’ve added new browser versions including Chrome version 90, and Firefox version 88. These versions are set as default.

New browser versions now available

What’s new for May 2021?

[Performance / Functional] Quick search for tests and reports

We’ve added a new Search field to Performance and Functional tabs! Now you can quickly search within the tab for tests and reports by their name, without having to go through “Show All Tests” or “Show All Reports” side bars.  

The field will display top 5 recently updated tests, and top 5 recently executed reports that match your search. To see the full list of tests or reports, click on “Show All Results” which will open the full list in a sidebar.

Looking for a more complex search, a way to find a test created by a specific user or during the last month? Stay tuned; We will add advanced search options to this field soon.


[Taurus / Performance Testing] K6 and Vegeta executors added

Taurus has added new executors: K6 and Vegeta. Now you can run your K6 and Vegeta scripts in BlazeMeter.


[Taurus / Performance Testing] MQTT protocol support added

Taurus has added support for the MQTT protocol. Now you can load test your IoT product with BlazeMeter.


"Disk Out of Space" Alert for Private Locations

Software updates require free disk space to be installed, and now you can get an alert and take action before free disk space drops below a threshold of your choice. To create an Agent alert, go to the Alerts page in Workspace Settings menu, and create a new alert. Like Test alerts, the notification channels for Agent alerts are Email, Slack, or both. Once an Agent alert is defined, you will be notified in case any agent in any private location in your workspace goes below the threshold.

For more details, see the documentation.


[API Monitoring] Enhanced Authentication for Client Certificates in API Monitoring Tests

We have enhanced the PEM-encoded Client Certificates based authentication, for API Monitoring Tests, to also accept a key file or a passphrase. 

You can optionally set up the passphrase as a Secret at the team or bucket level using the Secrets Management feature. This ensures that the passphrase need not be shared with every member of the team and is also not visible in Tests. This ties together two powerful features within BlazeMeter API Monitoring, designed to monitor your secure APIs and keep your API Tests secure.



Check out the docs to learn more. Requires a qualifying plan. Contact Sales to add Client Certificates support to your account.


[Performance Testing] Comparing performance tests to a Baseline

Comparison capabilities in performance testing are now enhanced with the option to define a Baseline for a test. Defining a test run as a baseline helps testers make sure the application performance remains stable as code changes. 

A test run can be defined as a Baseline from the (redesigned) test history tab, or from the report itself:



Once a baseline is defined, following test runs will be compared to the baseline, making it easier to identify degradations and bottlenecks, finding the related changes in code, and quickly taking actions to resolve them. You will find comparison data in the report Summary and in the Request Stats tab: 



The Compare Report page and the Trend Charts tab in the test will display a visual representation of the comparison to the baseline.

BlazeMeter also helps you automate the decision making process, by allowing you to configure the failure criteria Threshold as a deviation from the baseline, so that test runs that significantly deviate from the baseline will automatically be marked as "Failed". To do that, check the “Use from Baseline” checkbox in the failure criteria section in the test, submit the deviation you are willing to accept, and the Threshold will automatically be calculated based on your selection. 



Watch a brief demo on the Baseline Comparison feature:

For more information, see the documentation.


[Mock Services] Inspection View for Transaction-Based Mock Services

Understanding which requests and responses were handled by your Mock Services is critical in cases when there is a need to debug why certain requests were or were not returned by a Mock Service. BlazeMeter Mock Services now provide an "Inspection view" for transaction-based Mock Services, which displays details about recent traffic handled by a specific Mock Service.

You can now quickly identify specific requests by full-text search and display corresponding response details. The Inspection view also includes responses served by real service in case of “redirect to live system” no match mode is selected. Such responses from live system can be saved as new transactions and pushed to the running Mock Service directly from the Inspection view screen.

For more information, see the documentation.


[Mock Services] Filter Mock Services by Status

Mock Services view now provides a “Filter by Status” option which helps in cases where there are many Mock Services defined. By using this filter option, it is easy to display a subset of Mock Services based on a certain status. For example, you can display only Mock Services that are running or stopped. More details here.


[Mock Services] Display Historical Reports for BlazeMeter VSE Mock Services

Reporting for Mock Services running on BlazeMeter VSE now gives you the option to display reports for Mock Services that were previously running, but are now no longer available. This is useful if there is a need to display historical reports for Mock Services that were deleted. However, it is still important to understand how many transactions they handled or what were their hits per second characteristics.

To use this functionality, simply open a new analytics tab, define the desired time period and select "Mock Service" from the list of available Mock Services that were running in that particular timeframe. More details here.


[Mock Services] Export Reports to PNG or PDF 

It is a very common need to share reports with others or store them for your own reference. Reports for Mock Services running on BlazeMeter VSE can be now exported and downloaded as PNG images or PDF documents. More details here.


[Mock Services] Download vse_matches Logs from BlazeMeter UI

It is possible to download vse_matches logs for a selected BlazeMeter VSE directly from the Environments screen. More details here.

[Mock Services] BlazeMeter VSE Support for Istio

You can now use Istio to help route Ingress traffic into the desired pod in containers and the cluster. More details here.