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.
We’ve added a new browser version - Firefox 84.
Choose only the useful columns you want to see for your tests in a project. We've also added the last 10 test run results and columns configurator to the project page. The new “Last Results” column allows you to see a bigger picture for your project and quickly navigate to a test run.
Browser sessions dropdown in a GUI test report used to have a limitation of max 100 sessions. Now, you’ll be able to see all the sessions of your tests with high concurrency.
You can now search all items beyond those currently available on screen when you search at “Show all reports” and “Show all tests” tabs.
Starting with Taurus-cloud version 1.20.121, there is an automatic page load waiter executed after each Taurus action. This was added to make Selenium tests execution more reliable with less false negative results. As well as to align with Chrome Extension debugger behavior.
We’ve added new browser versions including Chrome version 87, and Firefox version 83 - these versions are set as default.
Now the account logo will be shown as a default in the thumbnail of the Executive Summary reports. To upload a logo, go to settings, click on the account name and add the logo URL:
To keep with our strong password policies, all new users will be required to choose a password with at least 1 special character.
We’ve added a new option to the Network Emulation configuration in a test, allowing you to limit the bandwidth per engine.
Due to browser image improvements introduced in previous releases, we lowered the suggested CPU and RAM requirements by halfs to 1 CPU and 1024 RAM instead of 2 and 2048.
We’ve added new browser versions including Chrome version 86, and Firefox version 81 - these versions are set as default.
Now it’s possible to filter recent test runs by project in the workspace dashboard.
Number of improvements were implemented in latest Charmander image release (v 2.7.7):
Previously, we released the default browser option for Private Locations. Now you can select the default browser version for a Public Location as well. The default version is set to be the latest BlazeGrid browser version (Currently chrome: 85, firefox: 80). When we release new browser versions in Blazemeter, your test will automatically switch to the latest available browser version, so, you don’t need to manually update the browser version for all your tests.
Now you can view more information in your test result email subject! These include
details on the workspace, project, test name and the test result as “failed” or “passed.” In case the failure criteria was not set or a test ended with no data, your test result will be listed as “completed.”
You can then use these to create relevant rules in your inbox and make your process even more efficient.
We’ve added new browser versions including Chrome version 88, and Firefox version 80 - these versions are set as default.
Our latest addition to Mock Services is the introduction of BlazeMeter Virtual Service Environment (BlazeVSE) – the Service Virtualization/DevTest VSE is now available as a single-click on-demand provisioning option from BlazeMeter CT platform – available in form of Docker container and also ready for seamless deployment on Kubernetes.
Highlights of BlazeMeter Virtual Services Environments:
Find out more details about BlazeVSE in the recent blog article.
Up until now, the pass/fail module in the yaml script was ignored by BlazeMeter, and users had to redefine it in the Failure Criteria section in the test configuration UI. With this new feature, we are translating the majority of Taurus pass/fail capabilities into Blazemeter’s Failure Criteria, so that when a yaml script is uploaded to Blazemeter the pass/fail module in the script will automatically appear in the test UI.
Now you can also execute a test from Taurus with cloud provisioning, and the pass/fail module will be recognized by BlazeMeter and displayed in the report.
Now you can control and define a list of multiple subscribers to receive the test results email once the test run ends. To add people, just search other users in the workspace by their name or email address.
Your test configuration is still in progress and you don’t want all subscribers to receive the email of this specific run? No worries, before the test starts, you can choose to send the test only to yourself:
Similar to the docker run command, the agent (ship) creation now provides an option to select the Kubernetes templates for roles and deployments used in the Kubernetes setup or the command to run the native Windows (non-docker) environment.
Note that the Kubernetes template will require input from the end-user to properly prepare the yaml for use.
We’ve improved the Kubernetes onboarding by providing an API that returns the service YML needed to deploy BlazeMeter’s ship on Kubernetes. Simply fill in the needed parameters and run the below command:
Curl https://a.blazemeter.com/api/v4/private-locations/<private_location_id>/ships/<ship_id>/k8s-command -X POST --user <Access_key>:<Secret>'
Example output (YML):
- name: AUTO_UPDATE
- name: CONTAINER_MANAGER_TYPE
- name: HARBOR_ID
- name: SHIP_ID
- name: AUTH_TOKEN
- name: A_ENVIRONMENT
namespace: ***USER INPUT REQUIRED***
- apiGroups: [\"\"] # \"\" indicates the core API group
resources: [\"pods\", \"services\", \"endpoints\", \"daemonsets\"]
verbs: [\"get\", \"list\", \"watch\", \"create\", \"update\", \"patch\", \"delete\", \"deletecollection\", \"createcollection\"]
We’ve reduced the size of the Taurus-cloud image from 15.8 to 6 GB and the size of the Taurus-cloud-slim from 10.3 to 4 GB.