added

Support for basic math calculations

Posted by Simon Choy 3 months ago

You can now apply basic math operations on numbers or variables without using Javascript snippets! There is a new syntax to support the math operations, e.g. {{1 + 1}}. mabl will attempt to evaluate the contents within {​{ ... }} as a math expression and return the numerical result. If you want to perform the mathematical operations on a variable, you can use the syntax {​{@​variable + 1}}. If you want to use multiple variables in the calculation, you can! Simply type in the expression within the {​{ ... }}, e.g. {​{@variable1 + @variable2}}.

added

Pass a unique Test Run ID as a variable in your tests

Posted by Patrick Hanbury 4 months ago

The test_run_id is now an available variable for mabl tests to aid in identification of mabl traffic. The test_run_id is a uniquely identifiable variable associated with a cloud test run. This variable is different from the test-id used to trigger CLI runs as each cloud run of the same test will have a different test_run_id.

improved

Dashboard performance chart now uses speed index

Posted by Geoff Cooney 4 months ago

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.

improved

View your remaining run allocation

Posted by Andrew Mendelsohn 4 months ago

Now you can view your remaining prepaid runs from the Usage tab in Settings.

improved

Retry on failure retries regardless of prior plan state

Posted by Geoff Cooney 4 months ago

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.

added

Element Screenshots on Output Page

Posted by Corey McCue 4 months ago

We've added element screenshots to the step cards on the test output page.

improved

Random variables in DataTables

Posted by Geoff Cooney 4 months ago

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

added

Save conflict for collaboration

Posted by Victoria Yang 4 months ago

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.

improved

Test Output Page Updates

Posted by Corey McCue 4 months ago

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.

added

mabl Bamboo app now supports remote agents

Posted by Don McNamara 4 months ago

The latest release of the mabl Bamboo app, version 0.1.4, has added the support for remote agents.