Ever wished you knew exactly who and what pull request triggered tests in the mabl cloud? Ever wish you could drill directly from the mabl UI into your GitHub assets? Now you can! 🎉

The mabl desktop app 1.3.17 release contained a number of improvements to authentication handling, including:

You can now filter your Release Coverage results more easily using predefined date ranges. Filter results to the last 7, 14 (default), 30, or 60 days, or use a custom range for more control.

Less than a month ago we introduced our brand new Microsoft Teams integration, which allows you to receive all kinds of updates in a channel of your choosing.

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

You can now access the total time your app took to load during a single test run as measured automatically by mabl. This can now be found by clicking "View all" at the top of any test output and looking for "Cumulative load time," in addition to the cumulative data available from the Performance tab of any test as well as the new Release Coverage page. As a reminder, this metric is what users would perceive as your app's overall load time for an entire test run. The feature is available for all enterprise and trial accounts, and is populated by Chrome tests run as part of a plan in the cloud.

You can now view the newest pages that have been added to your coverage report. Navigate to the "Newest pages" to see all of the pages added for the selected time period.

You can now set a workspace level target for cumulative tests run within the Release Coverage dashboard. This is a great way to track progress for your team and clearly communicate your testing goals. All you have to do is click the edit button in the top right corner of the chart and either enter a value in the modal, or choose to remove your target.

We're happy to announce that starting today mabl integrates with Microsoft Teams!

The scenario name associated with each test run is now visible from the test run history page. This is very useful when you have a DataTable with more than two scenarios as it can help you to easily identify differing test results for a particular scenario run.