Our enhanced welcome wizard makes it even easier for all new users to get started running their first tests. Anyone who is invited to an account, or signs up for the first time, will receive the following welcome screen to run a demo test.
We’ve also added direct access to BlazeMeter University via the homepage and booting screens, so you can easily continue your BlazeMeter learning with these free courses.
[Performance] Not enough resources
If you run performance tests on a private location, you have probably got a “Not Enough Resources” error when trying to run your tests - at least once. There can be many reasons for a test to fail running on a private location, like zero active agents or zero agents defined... but most of the time, it’s because the private location doesn’t have enough capacity or virtual users to run the test.
We’ve turned this error into an actionable insight, by additional information and advised next steps; We’ve added the name of the private location - because there can be more than one in the test, a link to the private location configuration – for easy access, and the number of users the test needs from the private location. But most importantly, we’re now differentiating between cases when other tests are running in parallel and consuming the private location resources, and cases when the private location is simply configured to run less users than requested in the test. This differentiation clarifies whether waiting a bit would solve the problem, or the private location configuration must be changed.
With this additional information you can now quickly and easily understand the problem and fix it!
[Test Data] Introducing Test Data Orchestration
BlazeMeter Test Data extends its functionality by Test Data Orchestration – the ability to interact with a test environment or external systems and components in order to:
Seed (write, publish…) generated test data into the test environment to run data-driven tests with consistent test data. Say bye to invalid test runs caused by out of sync test data.
Read (fetch) test data from external systems during the test start-up to drive test by the test data already seeded to the test environment or get that way test data provided by external systems.
Combine both sources of test data – generate and publish some of the data, read back other data from the test environment, combine both and use it for test. You can even sync it with associated data-driven Mock Services.
Validate correctness of existing test data at the beginning of every test run in order to avoid invalid test runs caused by expired test data.
Clean up your test environment automatically when test execution finishes - so your environment is ready for another test run.
For more details check BlazeMeter Test Data Orchestrator deep dive video, blog post and BlazeMeter Test Data Orchestration documentation.
[API Monitoring] Optionally disable DNS pre-check
Radar agent currently performs a DNS pre-check before sending any actual HTTP/s request. If the hostname of the request is unable to be resolved by the local DNS resolver of the system that the agent is running on, the entire tests will fail with an error message. This causes issues for users who want to use a proxy to access hosts that are not directly accessible by the system that Radar is running on.
As of Radar agent version 1.9, you can disable DNS pre-checks by through command line interface or config file.
Follow the BlazeMeter Guide for more details how to disable DNS pre-checks.
[API Monitoring] Display user who executed test
In cases when a test is executed in an ad hoc way via UI, it is useful to know who actually executed that specific test run. API Monitoring UI now displays such information for the test executions triggered from UI – both on the test run details screen as well as in the Results table.
[API Monitoring] Show test retry indication
Scheduled tests could be set in “Retry on Failure” mode. In such case, a failure in test execution is followed by one additional test re-run as a “retry”. Such retry test runs are now indicated in Results table as well as in Recent test runs view. In addition, the “Retry of” indication is clickable and opens the detail screen of the parent test run that failed and triggered that particular re-run.
[API Monitoring] Display agent version
API requests triggered by API Monitoring now contain information about the specific version of the agent that triggered the request. This information is especially useful for debugging and investigation purposes where there could be a difference in behavior between different versions of the agent.
[Performance] Filtering labels in Executive Summary
Occasionally when sharing Exec Summary with a team member or a manager, you need to focus on specific data in the test. And when it comes to large tests, with hundreds of labels (BlazeMeter supports up to 900 labels in a test) - the ability to emphasize specific labels is almost mandatory.
Starting this month, we’ve added filtering capabilities to the Aggregate Report section of the Executive Summary. Simply generate the report, select the label(s) you want to focus on, and the data will change accordingly.
[Mock Services] Select All option for transaction lists
The number of transactions you create for your Mock Services grows over time and as a result you deal with having to manage tens or hundreds of transactions. Which may be a tedious task, especially when you need to perform any bulk actions like tagging or moving on your transactions.
Therefore we have added a new “Select All” option to make your life easier when dealing with bigger collections of transactions and the bulk actions performed on them.
[Test Data] Built-in US SSN data generator function
BlazeMeter now provides a built-in synthetic data generator function for generating US social security numbers that conform to the rules and format of US SSNs. There are two functions for that: Use usSsn() to generate SSNs in the format used before 2011 which may be driven by an area code. Or use usSsnNew() for SSNs in the format used after 2011. Check our Test Data Generator Functions reference guide for more details.
Using software design patterns can improve the quality of all types of code, including test automation code. Learn the basics of design patterns & how they relate to test automation.
Security is at the top of BlazeMeter priorities. With SOC2 compliance achieved, we take our dedication to digital security to the next level.
This blog will explore the various Selenium framework types, when to use the Selenium framework, and how to get started.
Eliminating environment constraints is exactly what mock services do. In this blog post, you will learn how to replicate the Twitter/X API with BlazeMeter.
