We’ve made it easier to see where members in your account run their tests by adding the ability for account admins to see a graph representing the locations utilization spread between all the test runs in the account.
Any Ship that hasn’t been connected to BlazeMeter for over 3 months (e.g. server was offline, no network connection etc), will be marked as detached and unable to be used in the system for future test runs. If your Ship has been “detached” you will need to re-generate it or create a new ship.
Check out our sleek, new design in the top header for accessing your personal setting. Navigate from the top header to personal settings, to access the settings screen where you can change things such as your name and password.
You can now view all your account invites directly from the header. Just click on the envelope icon, and you’ll access the notifications. You can then choose to accept or decline.
We added extra filters to the admin view so you can now see results by workspace or by location.
We added a description column to the project page to make it easier to understand the tests created..The description is fetched from the test’s description which is added in the test creation page.
We’ve upgraded our engine images to support Taurus 1.13.6
We added two separate tabs for Functional and Performance Tests, so you can easily navigate between your functional and performance tests. When clicking on each tab retrospectively, the tests and reports are filtered, but the projects, workspaces, and all other account information can be accessed the same way.
You can now get a live view of the last 300 lines in you JMeter logs live for V4 tests. This can be found in the log tab, in application view of the tail, to allow for easier debugging.
For a BlazeMeter account admin, it’s important to have full visibility on the usage and resource utilization on the account level. The new admin view can be accessed from the top-right from any workspace dashboard, and allows account admins to see all tests that are currently running, including their details. Account admins can also choose to stop any tests directly in this new admin view. We are expanding this admin view to include more information such as location utilization.
Have access to tens of projects and you can’t find the one you are looking for? In order to help you navigate and find your projects, we’ve added a search capability in the projects page to easily find what you are looking for.
We modified the default location in the new created test to be US East (Virginia) in Google Cloud. You can then choose your desired location from the same list.
Need different engine sizes for different testing purposes? No problem! Account admins can now control the Engine size (CPU & RAM) and have different engine “types” from various locations. We will soon be adding the option so users with “tester” permission/role will not be able to access the Private Locations configuration.
New design and architecture for Remote Control update during test run allows you to update JMeter parameters for every scenario and location simultaneously. Furthermore, if a test has multiple scripts and locations, we will divide the RPS relatively between the scenarios and locations, according to the VUHs configured per location \ scenario
We’ve upgraded our engine images to support JMeter 5.1
Users now have full visibility & management on scheduled tests across each workspace they are part of.