What’s New for November 2023? 

[Mock Services] : Configure different data profiles for different mocks in the same service 

A mock service is often used across multiple testing environments like dev, test, QA, pre-prod and so on. If the parameters have hardcoded values in the various transactions of the mock service, then for each testing environment it is a manual task to update the values — which is a tedious task. Here, the new Configurations tab comes to the rescue with the ability for different profiles to be added for different testing environments by defining the name-value pairs, thereby externalizing them and moving away from the hardcoding approach. 


[Mock Services]: Mark optional params in Request Matchers 

For any request that comes into a mock service, there will be request parameters sent. Frequently, there will be some parameters that are not sent while others are. Now we have the ability in the Request Matcher for Body and Query Params to mark parameters as required. To indicate that the parameter is optional, uncheck the Required checkbox field. This would mean if the incoming request had those params they would be used for matching, but if they are missing then they are not considered for matching as they are marked optional. 


[Performance]: Change the number of users at run time 

Change the number of concurrent virtual users during load testing to enhance the quality of performance insights.  

This approach provides an enhanced view of an application's behavior under various conditions, helps in uncovering latent issues, and contributes to robust application performance optimization. Testers and developers alike can use this technique to fine-tune their applications, ensuring seamless operation even during periods of high user demand  

We’ve also enhanced the tracking and logging of Concurrency, Limit RPS and JMeter property changes by presenting the time and details of such changes under the Request Stats report. 

Follow BlazeMeter guide for more details. 


[Performance]: Engine Health Metrics - Alerts and Recommendations 

When conducting performance tests, it is recommended to maintain average CPU and memory usage below 70%. We’ve enhanced our in-app Engine Health monitoring and problem-solving capabilities by providing real-time alerts in case high levels of CPU or Memory have been reached.  

The alerts thresholds are set to 80% for CPU and 85% for Memory. These averages are calculated using a 60-second moving average of the data points collected throughout the test duration, for each engine. 

If the average of the 60-second moving averages recorded throughout the entire test duration surpasses the threshold set for a particular resource type (CPU or Memory), an on-screen real-time alert will be displayed. 

At run time, the alerts contain a link to the Engine Health tab, where we added filters to detect engines with high levels of CPU or Memory to make the debugging process more effective.  


Upon test end, a recommendation screen will become available with our recommendations to auto-remedy High CPU issues for relevant scenarios. Accepting each recommendation will automatically change the Max Number of Users per engine value, a change that with high certainty will improve the CPU utilization of future test runs. 

Follow BlazeMeter guide for more details.