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