### What it does The action scans the selected website for changes after the deployment and produces the results in the form of a visual comparison of the previous and current version of the page. ### How it works The action compares the currently deployed version of your site with the previous one. If the tests detect changes, it stops the pipeline and waits for them to be manually approved – a useful feat to avoid messing up the production server. ### Visual Tests Action Features - The action allows you to select the Browser and define: the Resolution in which the tests will be performed, the acceptable Pixel tolerance level and Images history limit - You can define who is allowed to accept visual changes and limit the scope to individual developers, administrators, or a specific group of users - You can exclude parts of the website (such as advertising banners) that will not be tested by entering their coordinates - The action can be configured in [YAML mode](https://buddy.works/docs/yaml/yaml-gui). See [${action.name} YAML parameters](https://buddy.works/docs/yaml/yaml-actions/visual-tests) and [${action.name} YAML config example](https://buddy.works/docs/yaml/yaml-actions/visual-tests#yaml-example-for-visual-tests) - Buddy's [${action.name} API](https://buddy.works/docs/api/pipelines/create-manage-actions/add-action/visual-tests) is supported - The action supports conditional execution: it can be run on each execution, only if there are changes in the repository or specific paths since last execution or if an environment variable has a specific value - Error handling: you can either stop the execution, mark action and pipeline as failed or proceed the execution, mark action as warning and jump to the next action ### More about ${action.name}

Visual tests

Visual tests Tutorials

Website and Server Monitoring with Buddy's Recurrently Executed Pipelines