[Performance] Displaying test scheduler owner as the owner of the report 

Managers reviewing the Executive Summary need to know who ran the test so that they can ask the tester who is responsible for more info when needed. The “Executed By” field in the Executive Summary indicates just that. 

Until now, this field displayed the user who ran the test when the test run was triggered manually or through API. 

From now on, the same logic will apply when the test run is triggered by a scheduler; Users using the test scheduler to trigger their tests will see the scheduler owner in the “Executed By” field as the go-to person for the report. 

[Performance] Welcome page customization 

We’ve added the ability to customize the content on the Welcome screen via API.  
By default, any user that accepts an invitation to an account without being added to a workspace will see BlazeMeter’s Welcome screen with an option to click a “Contact your account admin” button. This button currently directs users to send an email to their BlazeMeter account admin. 

The new functionality will allow account admins to change and replace the content of the button. 

Use the following PATCH API to disable the button, replace the button label with the required text, and mark the text with a hyperlink to the defined URL: 

PATCH - https://a.blazemeter.com/api/v4/accounts/<Account_ID> 

Body (example): 


"welcomeScreenLinkText": "Please follow these instructions", 

"welcomeScreenLinkUrl": " https://www.blazemeter.com” 


FEB Update


[Mock Services] Stateful Mock Services 

BlazeMeter now proudly supports Stateful Mock Services. This unique functionality takes Mock Services miles ahead of all our competitors. A tightly coupled integration with BlazeMeter Test Data makes Stateful Mock Services a compelling solution in solving the huge gap that shift-left testing had till today. Stateful-ness refers to the ability to not only persist state (data) across the Create, Update and Delete operations but also to retrieve the state within the execution of a Mock Service. In addition, Global Test Data variables can be set and also be incremented. 

As an example, consider a banking application that is using Mock Services as the backend for testing. Consider a use case where a new user applicant applies for an account, add and withdraws money and then chooses to close his account. When that new user applicant is approved, a new entry for this user data will created (user details are persisted). This user will then add money to his account (balance is persisted) and then withdraw money from his account (balance is persisted) and then this user account is closed and the user is deleted from the system (previously created user that was persisted is now deleted). During this test, Global variables can also be set and incremented.  

One of the highlights of Stateful Mock Services is that data persistence occurs when the Mock Service goes down or is shutdown. Whenever the Mock Service restarts, it is able to retrieve the persisted data.  

[Test Data] Test Data Management Page  

The new Test Data Management page lists all Test Data Entities stored in the workspace and displays their usage in BlazeMeter tests and Mock Services. The Test Data Management page also introduces a rich editor with auto-completion feature to speed up the creation of complex test data generation rules.

Image 2 FEB Changelog


[Test Data] Test Data Variants  

The new Test Data Variants functionality lets you define multiple instances of test data about users, orders, accounts, or any domain object that is relevant for your testing and makes it easy to switch between them.  

Test Data Variants are available for tests as well as data-driven mock services. Each Test Data Entity can have one or more Test Data Variants to keep your test data well organized without the need to create duplicates of existing Data Entities. Use Test Data Variants to create, bulk-edit, manage, and switch easily between variants of test data values, including negative test data. Simplify testing of various cases and increase your overall coverage. 

Image 3 FEB Changelog
Image 4 FEB Changelog


[Test Data] Add CSV files from Test Configuration to Test Data in bulk  

The ability to create new Test Data Entities from CSV files in bulk has been added to speed up creation of Test Data Entities. This is especially useful in cases when an existing test already contains multiple CSV files uploaded to the test configuration. 

Image 5 FEB Changelog


[API Monitoring] HTTP/2 support for test executions  

API Monitoring now supports sending requests over HTTP/2 which is extremely important for testing and monitoring newly developed services which are based on HTTP/2. As part of your test and environment settings, you can now choose to parse a request over either HTTP/1, HTTP/2, or to try HTTP/2 first and eventually fall back to HTTP/1.  

Image 6 FEB Changelog


For any request that was executed, the version of the HTTP protocol that was used is displayed as part of the test results.


Image 7 FEB Changelog


[API Monitoring] GET all groups in Team 

A new API endpoint now lists all groups defined within an API Monitoring Team. See the API Guide for more details about this new endpoint.