If your app was updated and you want to update the visual model in your mabl tests, you can rebaseline the visual model. Visual rebaselining, just like visual change learning, works per environment. When you rebaseline, mabl starts creating a new visual model. Until the dynamic visual model is ready, mabl uses the default visual comparison: current run to previous run.
Retirement of visual change learning
Visual change learning for browser tests will be retired on May 21, 2026. On that date, mabl will no longer:
- Flag visual changes on browser test steps in plans
- Generate visual change insights for browser tests
- Create dynamic visual baselines with diff highlights
To understand visual changes between test runs, we encourage you to use failure analysis and conversational results analysis. This retirement does not impact visual tests, which will continue to be available as they are today. Learn more.
Rebaselining within a test
If you want to start creating a new visual model for a specific test, you can rebaseline individual steps or all steps from the test output page.
The options for visual rebaselining are located in the Actions dropdown of step-level output. These options are only available if visual change learning is enabled for the plan.
Visual model rebaselining
If you don't see rebaselining options in the Actions menu, make sure that visual change learning is enabled and the step has formed a dynamic visual model. Learn more here.
Rebaselining multiple tests
If you want to rebaseline the visual model for many tests at a time, you can use the Deployment Events API to trigger a deployment with the option rebaseline_images set to true. This option tells mabl to start creating a new dynamic visual model for the targeted tests.