We have now added support for the creation of random data in variables. Now you can create variables with random names or addresses (and more!) using the string template. The syntax for this new feature is in the form {{fake.type.subtype}}, e.g. {{fake.name.lastName}}.

The mabl-cli v0.6.50-beta is out with a couple enhancements for the headless runner. The mabl-cli now supports executing API steps and mabl mailbox email steps in headless mode. Any tests using these two features can be executed with the --headless flag when running them via the mabl tests run-alpha command.

With the mabl-cli v0.6.52-beta you can now use the --from-plan-id flag with the mabl tests run-alpha command as a way of specifying the grouping of tests to run locally. This flag will use the plan info as a grouping of tests to execute sequentially.

The 0.0.23 version of mabl Jenkins integration plugin has been released.

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}}.

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.

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.