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

The default "Visit home page" test will now include an accessibility check. This feature allows your team to gather regular feedback on accessibility without any additional effort. Accessibility violations will be available in the Accessibility dashboard, but they will not cause the "Visit home page" test to fail.

Since Node .js v12 LTS support went end of life on April 30, 2022, the mabl CLI now requires a minimum Node.js runtime version of v14 LTS or higher. Starting with CLI release v1.24.0 users should upgrade to Node.js v14 LTS or v16 LTS.

We are excited to announce that a flexible timer for test trigger repetition is now available! Before this change you were allowed to select among limited options. With this improvement, you can customize the period of time you want a plan runs. If you choose to add a trigger, the minimum amount of time is 5 minutes and the maximum is 168 hours (7 days).

Mabl now supports downloading results of an accessibility check in JSON format. Simply click on the ACTIONS button and choose the corresponding menu option to download and share with your team!

Keep track of your accessibility check runs to date alongside your browser and API response usage. Similarly, mabl will also predict your usage for the end of the month.

We are excited to announce that mobile web testing for Chrome is now generally available!

As part of our ongoing work to improve Branching & Merging in mabl, we've recently released the new Branch Details page. This page provides a summary of changes made on the branch including:

Two new commands have been added to the CLI starting with version 1.22.1 for managing Link Agents: list and terminate

Today a change was released to the Desktop App (v1.11.6) and Unified Runner to make cookie interactions in the trainer and Unified Runner match the behavior of the Legacy Runner. Specifically, when making a cookie assertion, removing a cookie, or clearing cookies, your test will now only see cookies that the current page has access to. Previously the trainer would show all cookies in the browser, which could cause problems for cookies with common names that might be present on multiple domains. It is possible that this change may cause some tests to fail if they were depending on the previous behavior. If you need assistance resolving any issues with the new cookie behavior please reach out to our support team via the in-app chat.