Based on your feedback, we've improved the UX for recording mode in the Trainer to clearly identify whether mabl is in recording mode.

You can now set failure reasons for multiple tests at once, either by setting a failure reason for all failing tests in a plan or deployment, or by selecting the specific tests you want to categorize from the Results page.

Wait until steps and configurable finds have been enhanced to allow you to fine-tune the criteria that mabl uses to find an element.

When creating tests, you can now guide mabl to select an element based on specific properties. If your application has multiple elements with similar qualities, such as lists, tables, or grids, mabl will prompt you to provide additional context for the selected element. Including the intention behind a selection can increase mabl’s confidence in locating these elements, especially if the content or position is likely to change. This also reduces the need for custom finds using XPath or CSS. Read more here.

The mabl coverage page now combines the same path, such as /workspaces, across hostnames and environments. This means that this /workspaces page will no longer be duplicated for each environment that you're testing in the cloud, such as app.myapp.com, dev.myapp.com, or qa.myapp.com.

After extensive validation testing, Google Chrome v85 is now available as the default version of Chrome used by mabl's cloud test runs.

It's now easier to add or remove tests from plans! Rather than selecting items one at a time, we've changed the selection to checkboxes to allow you to seamlessly add or remove a test from multiple plans at once.

We've added the ability to exclude unwanted or unrelated parts of your application by URL path from coverage metrics and reports. This feature can be used to exclude pages from your website's blog that you crawl for broken links, user-facing documentation, or parts of your app that aren't accessible to users yet.

If your bamboo installation requires that only the mabl bamboo plugin's requests be sent through a proxy or through a different proxy server than the bamboo server's default proxy, you can now configure the proxy settings within the deployment task configuration. Basic authentication is also now supported by this configuration.

While a test is starting or running, it can now be stopped directly from the output page of that test as it runs.