browse

Automating QA testing with a persistent headless browser uses a headless Chromium instance that retains state across commands and restarts. This allows you to execute navigation, interact with elements, and perform regression checks without losing session data during test runs.

Capturing annotated screenshots for bug reports during headless browser testing is fully supported. The skill drives a headless Chromium browser to capture annotated screenshots, generate visual evidence, and validate page state for bug reports and dogfooding deployments.

Headless browser testing works for verifying responsive layouts across devices by driving a Chromium session to check page rendering at different viewport sizes. It captures visual validation snapshots and performs DOM state checks to ensure consistent UI behavior.

The best way to start a clean environment for automated site dogfooding is to initialize a persistent headless Chromium session. This satisfies the requirement to start from a clean state while allowing you to reuse sessions and execute browser commands like goto and snapshot.

Inspecting page content and console logs during headless browser automation is done using built-in commands like text and console. These commands read page content, monitor network activity, and check DOM state to verify feature behavior and gather debugging evidence.

A limitation of using a persistent headless browser for regression checks is that retained state across sessions may cause unexpected caching or authentication carryover. You must explicitly manage session resets to ensure each regression check starts from a truly clean environment.