mabl now displays the speed index, instead of the perceptual speed index when displaying step performance charts. Both measures attempt to calculate the time until pages are fully loaded but use different mechanisms to compare renders. The lighthouse project has migrated away from perceptual speed index, in order to more closely align with other performance tools and mabl has decided to do the same. For more details on how mabl calculates speed index, see https://help.mabl.com/docs/speed-index.
Now you can view your remaining prepaid runs from the Usage tab in Settings.
Previously, mabl's retry on failure option for plans would only retry the plan if the plan was in a passing state before the run. We received some feedback that many customers expected it to retry failures regardless of the current state of the plan. As a result, we're updating the behavior to be more in line with expectations. This setting will now retry failures, regardless of whether the plan was in a passing state prior to being launched.
We've added element screenshots to the step cards on the test output page.
You can now use random variables in DataTables in mabl without needing to create an intermediate variable. Just use mabl's random variable syntax in your table values and mabl will resolve them before each test run. For more details, see our help docs here
With the new release, collaborating on tests with teammates is easier than ever with save conflict detection. mabl will now notify you when you are about to save changes to a test or reusable flow that will conflict with a save that another user has recently made. This helps prevent unintentional reversions of teammates' changes to tests and reusable flows, given the latter can be shared across hundreds of tests at once.
With this release, we're introducing a batch of updates to the test output page which are aimed at helping you be more efficient when analyzing the results of a test run.
The latest release of the mabl Bamboo app, version 0.1.4, has added the support for remote agents.
You can now use test labels to launch multiple test runs locally in headless mode from the mabl CLI. The --labels flag can be used with the mabl tests run-alpha command to select a set of tests and run them sequentially. You may also use --exclude-labels and --branch-changes-only similar to label options found on the run-cloud command.
Have you created a flow but wanted to use different values in the flow depending on the test that uses the flow? We have now introduced flow parameters! Flow parameters are variables that are scoped to the flow and they can be overridden for each instance of the flow as desired. To create flow parameters for a new flow, after filling out the flow name, you can click on the Parameters tab or the row indicating how many parameters are defined in the flow.