Increase test coverage across dropdown and list selectors in your application with the improved mabl select step, which gives you more control and flexibility over how you structure your tests.

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

Running tests via the mabl CLI is great! It's fast and you can do it headless mode without interfering with your desktop. Sometimes tests do fail though and you may want to rerun the test with the browser visible to see the failure. We added a new flag to the mabl-cli (1.1.10) so that you can keep the browser open after the test completes so that you can inspect the current state of the application with Chrome DevTools and figure out why the test might have failed.

Local tests runs through the mabl CLI (v. 1.1.6) now have the option to highlight elements as they are interacted with in the page. Specify the --highlights flag in your command to activate the playback highlights.

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.