# Visual Testing Published articles for Visual Testing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Practicing Playwright: Visual Testing With Playwright DevFeed: [Practicing Playwright: Visual Testing With Playwright]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-05-21T12:46:54Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [Testing](), [Docker](), [ci](), [WebKit](), [Chrome](), [Firefox]() Tags: [chrome](), [ci](), [docker](), [firefox](), [playwright](), [snapshots](), [software-testing](), [testing](), [visual-testing]() ### AI overview This tutorial demonstrates Playwright visual testing by capturing screenshots of pages or elements, comparing them with baseline snapshots, and using masking to exclude changing content. It also discusses browser and operating-system differences, repository size, and running visual tests in a standardized CI environment. ### Source excerpt If you want to do some basic visual checking to see if there has been any deviation from your baseline of images, you can use Playwright. It's built in! Playwright can take a snapshot of a web element, a visible viewport, or a full page, and save it in your Git repository as a baseline, failing the test if the image, page, or viewport does not match up. Caution: From what I have been reading, this can quickly cause your code repository to balloon in size, since Chrome, Firefox, and WebKit would each store its own golden screenshot in your repo. Also, images on Mac, Windows, and Linux all appear different pixel-by-pixel. If using a CI platform, it might be best to run visual tests only on a standard Playwright Docker image, to generate and compare snapshots. According to TestQuality, "Once a suite passes 50-100 visual tests, teams need a layer that tracks run history, surfaces flaky-test patterns across cycles, and routes confirmed defects into the team's tracker -- none of which lives inside the test runner itself"... I wonder if you can store images in an Amazon S3 bucket and hook that up as a virtual drive? ... no matter. That will be a blog post for another time... Right now, we will be walking through Butch Mayhew's code he wrote for his LinkedIn Learning course, Learning Playwright, found on his companion GitHub site. While the test is in a certain state you can a screenshot of the page or certain elements of the page and save them as a snapshot. The snapshots an be used as a baseline images to compare your current site against. This baseline can be periodically updated as the site evolves. How does this happen? With Playwright's .toHaveScreenshot( ) to take a screenshot and the mask method that you want to leave out of the comparisons between the expected and actual screenshots. toHaveScreenshot(name): Playwright.dev / Page Assertions Our Test Site: PracticeSoftwareTesting.com Butch has a series of tests for the test site Practice Software Testing ( practicesof ## Introducing Visual Testing in Maestro DevFeed: [Introducing Visual Testing in Maestro]() Original publisher: [Read original article]() Author: Dan Caseley Published: 2026-03-02T07:00:00Z Content type: release Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [Command-line interface]() Tags: [cli](), [maestro](), [regression](), [screenshot](), [screenshot-testing](), [screenshots](), [testing](), [visual-regression-testing](), [visual-testing]() ### AI overview Maestro's Visual Testing compares screenshots with saved baselines to detect unexpected visual changes. The article explains assertScreenshot, takeScreenshot, cropOn, and thresholdPercentage, and describes use cases including shared design-system components, dependency upgrades, dark mode, and complex layouts. ### Source excerpt Available in CLI v2.2.0, Maestro Studio, and Maestro Cloud ## Debugging Embedded Graphics with Wokwi and AI: Solving a Raylib Color Mapping on ESP32 DevFeed: [Debugging Embedded Graphics with Wokwi and AI: Solving a Raylib Color Mapping on ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2025-10-24T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [debugging](), [Simulation](), [Embedded Systems](), [Testing](), [Artificial Intelligence](), [Warp](), [ESP-IDF]() Tags: [ai](), [blog](), [ci-cd](), [debugging](), [embedded](), [esp-idf](), [esp32](), [esp32-s3](), [graphics](), [library](), [porting](), [practitioner](), [simulation](), [testing](), [visual-testing](), [warp](), [wokwi]() ### AI overview The article describes using Wokwi simulation and Warp's AI vision capabilities to diagnose and fix an RGB565 color-mapping bug in a Raylib port for ESP32 devices. It presents screenshot-based visual debugging, rapid iteration, and automated testing as alternatives to repeated testing on physical hardware. ### Source excerpt Learn how Wokwi simulation and AI-assisted debugging solved a subtle RGB565 color mapping bug when porting Raylib to ESP32, turning hours of hardware debugging into an efficient iterative workflow with automated visual testing. ## Why Visual Testing Is Critical for Mobile App Quality DevFeed: [Why Visual Testing Is Critical for Mobile App Quality]() Original publisher: [Read original article]() Author: Alex Zhukovich Published: 2025-03-13T20:59:10Z Content type: tutorial Language: en Sources: [Alex Zhuk - Android development and testing]() Topics: [Testing](), [Mobile](), [Android](), [App]() Tags: [accessibility](), [android](), [android-testing](), [app-quality](), [devices](), [mobile](), [screenshot](), [screenshot-testing](), [testing](), [tests](), [themes](), [ui](), [visual-testing]() ### AI overview The article explains that visual testing can detect UI imperfections that conventional UI tests may miss. It introduces screenshot comparison in Android, using baseline "golden screenshots" to identify alignment, color, layout, localization, and accessibility issues across devices and themes. ### Source excerpt Visual tests catches UI imperfections that traditional UI tests miss. They detect misalignments, color issues, and layout problems across different devices and themes. This article introduces visual testing concepts, explains how screenshot comparison works, and demonstrates implementation.