As mabl invests in agentic capabilities, including failure analysis and conversational results analysis, we are retiring visual change detection for browser tests on May 21, 2026.
On the retirement 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
- Show the visual change filter or labels on steps in browser test output
What is affected
The retirement applies to dynamic visual change learning for browser tests only. The following are not affected:
- Visual tests continue to work as they do today.
- Side-by-side before/after screenshots remain available for browser test steps. Only the highlighted diffs between the screenshots are going away.
Next steps
Moving forward, we encourage teams to use failure analysis and visual assertions to investigate visual or structural UI changes between runs.
For example, if you suspect a visual change caused a failure, prompt the agent to compare screenshots from the failing step to the same step in recent passing runs to surface patterns and insights in results analysis:
"Step 10 failed to find the 'Add to Cart' button. Can you pull up screenshots of this step from recent passing runs?"
Or add a visual assertion step to validate a specific appearance, such as checking that a specific layout theme is present:
"Ensure that the search results page shows a winter-themed background."
If you have any further questions or concerns about this change, please reach out to your CSM.