Suggest an editImprove this articleRefine the answer for “What is the goal of screenshot testing?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**The goal of screenshot (visual) testing** is to detect unintended visual changes in the interface and guarantee that the UI continues to look the way it should after updates to the code, libraries, browsers or styles. **Key point:** the test compares every new result with the reference screenshot and reports exactly what changed if the image differs.Shown above the full answer for quick recall.Answer (EN)ImageThe goal of screenshot (visual) testing is to **detect unintended visual changes in the interface** and guarantee that the UI continues to look the way it should after updates to the code, libraries, browsers or styles. --- The main task: **protect the appearance of the interface**. The test answers the question: *"Does the interface look just as correct as before?"* --- Screenshot testing helps: - detect visual bugs (shifted layout, a disappeared element, broken spacing) - capture the UI state and track any changes - avoid design regressions during refactoring, CSS changes or component updates - reduce the amount of manual visual checking --- **The essence:** there is a reference screenshot, and every new result is compared with it. If the image has changed, the test reports this, showing *exactly what* changed.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.