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.
We're happy to announce that you can now filter what you see in mabl by a set of applications. This filter is unique to each user, is easily changed, is able to be toggled on and off from the top of the page, and will persist between sessions.
View the full keypress step documentation for detailed usage.
You can now filter a journey's execution output to show steps that were completed using an auto-heal. An indicator of associated auto-heals on the journey run is also shown in the summary panel above the log output.
You can now easily identify which element attributes have changed in the Element History view on the test output page. Any attributes that have changed from one version to the next are highlighted. Additionally, you can click the icon in the lower right of the cell to compare exactly what changed from one version of an attribute to the next.
You can now rollback element history from the Element History view on the test output page. If you would like to rollback to an earlier set of attributes you can use the buttons in the left column to set any available row as the primary set and remove all history generated after it (items after appear above in the table due to sort order). This allows users to reset the tracked element attributes in cases where mabl may have auto healed incorrectly during a test.