mabl now highlights only the unexpected visual changes in the output for your journeys. mabl automatically learns what areas change across test runs and excludes them from visual change detection. For example, if your app shows event schedules or popular items that change regularly, mabl will recognize those areas and only highlight other areas when they look different from what mabl expects.
View, sort, filter broken links list for completed tests from the test output page.
Filter insights by archived/current status, insight type, application, environment, and URL on the dashboard.
Filter test results by status, application, environment, and URL on the dashboard.
Previously the Slack notification for working/broken plan executions did not include any context about which plan was fixed/broken:
You can now compose a new variable using existing variables, in addition to randomly generated alpha-numeric strings. In the example below, we extracted the text of an element and stored it in a variable named "email". Then we created another variable "url" with the "email" variable embedded, for testing the email verification endpoint.
You can now assert on element properties in the mabl Trainer. When configuring a comparison assertion (equals, contains, greater than, less than, etc.) you will now see a list of available attributes on the element to assert against other than 'innerText'. This allows you to assert things like the 'src' of your image, the 'value' of an input, whether a checkbox is 'checked', and much more.
Have you ever wanted to just record your journey and then go back and add assertions or waits later? Did you do want to take a different approach to the same result? You can now insert steps in journeys, making these things possible.
It is now possible to configure a Plan to run with either Chrome or Firefox. In order to configure the browser used at run time, edit an existing Plan or create a new Plan. You will now see a Browser field where either Chrome or Firefox may be selected.