Visual and functional testing complement each other to help you take a more holistic approach to testing the user interface (UI) of your application. While functional testing ensures there are no issues with app behavior, visual testing ensures that there are no issues with the overall look and feel.
In mabl, there are two types of visual change detection capabilities:
Visual change learning
When browser tests run as part of a plan, mabl uses screenshots to detect visual changes. If mabl identifies a visual change, the test step appears with a "visual change" label, and the screenshot includes a comparison to the visual baseline.
To create more dynamic visual models for comparisons, you can configure your plans to use visual change learning. And if your app gets updated, you can update the visual model through a process called visual model rebaselining.
Detecting visual change in a browser test
To learn more about how mabl builds dynamic visual models, check out the article on visual change learning.
Visual tests
A visual test is a standalone smoke test that visits a list of URLS and checks each page for visual changes, broken links, and JavaScript errors.
You can run visual tests to monitor key pages in your application across all supported browsers, get visual change insights, and review the test output for visual regressions.
Visual changes do not fail tests
When mabl detects a visual change, whether it is in a browser test or a visual test, it treats the visual change as a warning that does not cause the test run to fail.