All Safari tests running in the mabl cloud will now run on Safari version 14. This is an automatic upgrade, and there is no need to alter your existing tests, plans, or deployments to use the new version. Among other improvements, this brings improved support for file upload steps in Safari.
After extensive validation testing, Google Chrome v86 is now available as the default version of Chrome used by mabl's cloud test runs.
The Coverage page is now filtered by application to give you more visibility into how each of your individual apps is being covered by your testing. While this won't impact your overall coverage metric, you'll now be able to more easily determine which areas need more testing. Combined with the previous changes to group pages by path, rather than path and hostname, your coverage metrics should be more accurate and insightful than ever.
The plan labels and test branch options are now available in the Azure Pipelines task.
The 0.1.8 version of the mabl for Bamboo integration has been released. Now you can specify the branch of the tests to trigger. An issue related to duplicate test case IDs showing up in JUnit reports has also been resolved.
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.