Do you use the mabl Slack integration to notify specific channels when tests fail? Would you like mabl to mention certain users (such as yourself) in those messages so that they are alerted in Slack?
We're happy to announce that you can now filter the plan run history on your plan details page by status.
Coverage reports are now available on the coverage page under "Page reports". It's easier to see which pages have the most users and complexity and how much coverage they have (or lack), compared to the number of journeys covering each page. This may better inform which pages need the most attention from a testing perspective.
A little while ago, we introduced the application and environment summary tab under the "Configure" page in the mabl app. This tab allows you to manage your applications, environments, and the URLs that you're testing all in one place.
The mabl Coverage page will now report test coverage in terms of common pages of your application. We use a technique called "url-clustering" to group dynamic URLs of pages, giving you more accurate and readable coverage data on how mabl is testing your apps.
Building on the retry-on-failure feature for plans, there is now a new option that will cause only the failed tests to be retried when a plan goes from passing to failing. The new setting can be accessed after enabling "Automatically retry on failure" in the plan settings.
Now you can create assertions and IF conditions against template strings. Most notably, template strings can include references to variables.
mabl now saves off the filters you apply on the following pages: results by journey, plans, journeys, flows, snippets, insights, explorer, coverage, and datatable pages! When you apply filters on these pages, mabl also saves off the filter selections. The next time you visit the page again, mabl will apply the filters that have been saved off. For example, if you filter the journeys page to find a particular journey, view the journey details, and then come back to the journey page, the same filter you applied before will be applied again without you having to type it in again. The filters are saved for each user and workspace combination, so the filter will not be applied to the same pages in other workspaces.
Mabl now supports two new additional assertion types: ends with and does not end with. This allows - for example - to assert that the URL of the visited page ends with an expected value.