meow:browse

Headless browser testing for QA can persist session state like cookies and login sessions across calls using a dedicated headless Chromium instance. State persists between commands to simulate real user sessions for end-to-end validation.

Headless screenshots and visual diffs for site dogfooding are supported through annotated screenshots and diff rendering. You can navigate pages, interact with elements, and capture visual evidence to verify deployments and reproduce bugs.

Automating end-to-end validation of deployments with a headless browser is best handled through command-based navigation like goto, click, fill, and snapshot. The browser auto-starts on first use, then executes subsequent commands in around 100ms.

Responsive checks and page state verification in headless Chromium are performed through built-in snapshot and interaction commands. You can execute navigation, fill forms, capture annotated screenshots, and verify state across persistent sessions.

You do not need to install external dependencies to start the persistent headless QA browser. It requires no dependencies, auto-starts on the first call in about three seconds, and provides reference patterns for structured testing.

Headless browser testing sessions reset between commands if you are not using a persistent state solution. This skill maintains cookies, tabs, and login sessions persistently across calls to prevent state loss during end-to-end validation.