The Execution Results API has been updated to make it easier to tell whether a deployment was successful when taking automatic plan retries into account. A new top-level object was added to the response that looks similar to the following:
Selecting an application, environment, and URL for a plan just got easier.
We have updated the cards in the email workspace report to provide even better visibility into your tests, execution and recent insights.
You can now change the target element of a click, double click, or a hover step without the need to retrain the step. You just need to edit the step in the trainer and you should see a cursor button to change the selected element, details about the target element, and a dropdown to change the action type.
After importing/inserting an existing/named JavaScript snippet to a journey, do you often wonder what the snippet name was used in the journey? Now you can see its name in the step description!
With configurable finds, you can now tell mabl how to wait for just the right element to appear without writing any CSS or xPath. You can also control how long mabl will wait for a matching element (up to 15 minutes) before widening the search and auto-healing.
Integrating end-to-end regression testing as part of your CI/CD pipeline and developer workflow is about to become a whole lot easier with the mabl CLI, a command-line tool.
Have you ever wanted to export all the screenshots from a mabl test run to peruse offline or archive? Now you can with the mabl CLI.
We have updated cards on Dashboard and Insights screens to provide even better visibility into your journeys, test coverage, and execution.
In complex environments with many applications, environments, and credentials, just a name is often not enough to describe a configuration entity. You can now use descriptions to capture and share with your team additional information about your configuration.