Visual change detection

Once you train a mabl Journey that executes under a test Plan, mabl automatically starts capturing screenshots of the application UI state. You will see some of these screenshots in the Journey output, after mutating actions such as clicks, text entry and wait steps. It takes around 10 Journey runs for mabl to create a visual baseline model.

 

Automatic change detection

While mabl learns, you will see a message like the following.

Once mabl has finished creating the visual model baseline, it will start generating insights about visual changes as shown on the following image.

When you go to review a Journey output that has visual changes, you can filter for visual changes and review a side-by-side comparison against the baseline image with the differences highlighted.

You can review the dynamic content areas that mabl has identified by clicking on Highlighting --> Dynamic content.

Visual change detection


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.